System design · Key technologies: the tools you will actually name

Postgres as the default, and where it stops

A single well-run Postgres primary with replicas is the correct starting answer for most system design prompts, and the skill an interviewer is checking is whether you know what it gives you (transactions, isolation, indexes, JSONB) and the specific signals, such as write volume, connection count and replica lag, that tell you it is time for something else.

22 min read Full lesson in the app Patterns: postgres-default, lost-update, connection-pooling

What you'll be able to do

Before this: picking-a-datastore, replication-and-consistency, sharding-and-partitioning

Log in to read the rest of this lesson

A single well-run Postgres primary with replicas is the correct starting answer for most system design prompts, and the skill an interviewer is checking is whether you know what it gives you (transactions, isolation, indexes, JSONB) and the specific signals, such as write volume, connection count and replica lag, that tell you it is time for something else. This walkthrough runs about 22 minutes, with runnable code you can edit and re-run as you read. A new account gets 7 days of Pro free, no card required.

Log in to continue

The first module of every track is free to read on the web: see what's open in System design.