Skip to content

Why the boring architecture usually wins

Queues, boundaries and failure modes: distributed systems, databases, messaging, caching and scaling.

All notes

  1. , 8 min read

    Sharding vs partitioning

    Two words used interchangeably in meetings, and the operational difference that makes them not the same thing at all.

    • Databases
    • Distributed systems
  2. , 14 min read

    Designing a notification system

    Fan-out, user preferences and the retry budget — sketched end to end before building any of it.

    • Messaging
    • Distributed systems

Next

Have a system worth arguing about?

I am always up for a conversation about architecture, trade-offs, or a bug that refuses to die.

Start a conversation