Scale From 1 to 1M

Each rung appears only when a problem forces it. Read the problem first and decide what you would change before you look at what the rung actually is — the whole exercise is refusing to adopt a capability as best practice when you do not have the problem it solves.

A queue you added because a blog post recommended queues is not architecture; it is a second system to operate plus eventual consistency you did not need. Every rung below costs something, and the cost is only worth paying against the problem stated above it.

  1. Rung 1 · Start
    The problem that forces this

    You have no users and no problems. The only real risk is building for scale you do not have.

    What changes

    One instance, one database, deployed simply.

    What it buys

    Every operation is local. Transactions cover the whole domain. Debugging is reading one log.

    What it costs

    Nothing yet. This configuration is correct, and staying on it as long as it works is a decision, not an oversight.

    The Monolith →
1 / 10