Hacker News Reader

3. When [not] to use a database.

4. When [not] to use the network

A lot of the performance wins I have been able to pull off (1000x) were from removing unnecessary distribution and unnecessary databases.

View on HN

I'm curious (maybe some lessons or good horror stories there), what are people using databases for that they shouldn't?

$current_product has a table with 3 rows that is used for config. Every other table has a foreign key to this one. It was designed as a multi-tenant application that never got over 3 tenants. Other tables are over 1billion rows already. The 3-row table is mostly json columns, and is basically untouchable now.

Reply on news.ycombinator.com