Featured
Firestore is superb at keyed reads and poor at friends-of-friends. When a graph database earns its place, and how to keep two stores honest.
12 min
Topic 04 / 08 · 08 articles
About this topic
130 words
Data modelling decisions are the hardest ones to reverse. A document shape that is convenient for the first screen you build can force expensive fan-out queries forever after, and adding a second database solves one class of problem while creating two new ones.
The articles in this topic look at those decisions in detail: modelling Firestore collections for predictable, indexed reads; when a graph database like Neo4j genuinely earns its place next to a document store; how to keep two stores in sync with events and idempotent upserts; connection pooling for small services; and what happens operationally when a managed database decides to go to sleep.
Each piece ends with a clear rule of thumb for when the approach is worth it — and when a simpler option will do.
Featured
Firestore is superb at keyed reads and poor at friends-of-friends. When a graph database earns its place, and how to keep two stores honest.
12 min
· 12 min
Which Postgres schema changes lock a table, which are safe, and the three-release pattern I use to change a live column without an outage or a long window.
12 min
· 11 min
A jobs table, one claiming query and a lease column give a small team a reliable work queue on the Postgres it already runs. What to build, and where it stops.
11 min
· 10 min
The Cypher mistakes that return wrong results or fail late: subquery scope, UNION inside CALL, vanishing rows, WITH between writes, and numeric parameters.
10 min
· 12 min
Auto-pause saves money until the first request after a quiet weekend. What a paused database looks like to your app, and a design that survives it.
12 min
· 13 min
The Firestore limits that bite as a database grows, and the schema choices that avoid them: hot documents, index fan-out, ramp-up, pagination, rules and TTL.
13 min
· 14 min
Feed architectures on a per-operation database: query-time merge, per-follower inboxes and the hybrid. With the cost arithmetic and the Firestore code.
14 min
· 14 min
Twelve small Cloud Run services, each with a sensible pool, can still exhaust one Postgres. How to do the connection math and pick a pooler.
14 min
· 12 min
Firestore is superb at keyed reads and poor at friends-of-friends. When a graph database earns its place, and how to keep two stores honest.
12 min