Topic guide

System Architecture

System architecture in practice: monolith or microservices, database scaling, caching, zero-downtime migrations, and distributed systems.

3 topics · 17 articles

Monolith vs. microservices

When to split your system and when to keep it together.

Databases & caching

Scaling data: replicas, caching, migrations, and multi-tenancy.

Distributed systems

Consistency, availability, and communication between services.

Frequently asked questions

When should we move to microservices?

Once the monolith becomes the bottleneck, for deployment, scale, or coordination between teams. That usually shows up around 30 engineers.

Database scaling: vertical or horizontal?

Vertical first, because it is simpler. Move to horizontal scaling (sharding) only when a single instance can no longer cope, even with read replicas.

Should I use NoSQL?

Only if you need a specific NoSQL feature. For most systems, PostgreSQL is more than good enough.

ACID or eventual consistency?

ACID by default. Accept eventual consistency only where horizontal scale requires it, and make that explicit to whoever consumes the data.