Testing

Most applications start with a fairly simple architecture: an API service talking to a database. As the application grows, we start adding components such as a cache to speed things up, read replicas to distribute the load, perhaps a message queue for background tasks. Before we know it, we’re staring at a monstrous architecture that’s increasingly difficult to reason about. The final boss might involve a database sharded across regions, with replicas coordinating through a consensus algorithm to agree on the state of the system. ...