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
Tag
8 entries: Note, Essay.
Separating old records that bloat the live table: partitioning, cold storage, and keeping query access while you archive
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
Is the ORM making us lazy, or actually protecting us? The balance of safety, readability, and performance between the two approaches
A missing index slows the query; too many indexes make every write expensive. Striking the right balance by measurement, not by guesswork
Running migrations without causing downtime in production: backward-compatible steps, multi-phase column changes, and avoiding table locks
Before scaling up the database: moving read traffic to replicas, the traps replication lag creates, and when you actually need it
The consistency and data-integrity crises that projects which moved to NoSQL for the comfort of going schemaless eventually hit
Before adding a separate search engine, queue, or document DB: how far PostgreSQL gets you on its own, and where its limit begins.