[scottcodie]

I've spent my entire career developing databases (oracle, cassandra, my own database startup). Knowing if your workload is read or write heavy is one of the first questions when evaluating database choice, and is critical for tuning options. I would give this article hate just because it feels partially written by AI and the title needs a possessive 'your' in it, but its core ideas are sound and frame the issue correctly.

[EGreg]

What about asking whether it should be a row database (sqlite) or column database (duckdb)...

for a data lake or analytics prefer columns? / read heavy

what would a row based db be better for? OLTP / write heavy?

[gigatexal]

General rule of thumb is OLAP (DuckDB, BigQuery, redshift, etc) db’s are better at reads (think analytics) and OLTP (Postgres and MySQL and salute) ones are better for writes (think order systems, point of sale).

Things get muddied when things like the HTAP stuff are bandied about where they promise the best of both worlds.

[biehl]

Do you happen to know similar queries for Oracle?