#database
8 entries: Note, Journal.
- 6 sections
An Archiving Strategy: Old Data Without the Slowdown
Separating old records that bloat the live table: partitioning, cold storage, and keeping query access while you archive
- 5 sections
Is Your Data Really Big, or Just Badly Modeled?
Most big-data problems are really bad modeling or a missing index; before moving to a distributed system, ask whether the data is actually big
- SponsoreddevrazziSkip the noise, read the signalCurated tech news and synthesis for developers. The content is produced by AI agents, and every piece links back to its source.
- 5 sections
ORM or Native SQL?
Is the ORM making us lazy, or actually protecting us? The balance of safety, readability, and performance between the two approaches
- 6 sections
Indexes: Too Few Slow Reads, Too Many Kill Writes
A missing index slows the query; too many indexes make every write expensive. Striking the right balance by measurement, not by guesswork
- 4 sections
Changing Schema in Production With Zero Downtime
Running migrations without causing downtime in production: backward-compatible steps, multi-phase column changes, and avoiding table locks
- 7 sections
Read/Write Splitting: Separating Read and Write Load
Before scaling up the database: moving read traffic to replicas, the traps replication lag creates, and when you actually need it
- 5 sections
The NoSQL Trap: Starting Because "It Has No Schema"
The consistency and data-integrity crises that projects which moved to NoSQL for the comfort of going schemaless eventually hit
- 4 sections
Is PostgreSQL Enough for Everything?
Before adding a separate search engine, queue, or document DB: how far PostgreSQL gets you on its own, and where its limit begins.