Summary
In this chapter, we learned that modern systems need to work in an eventually consistent world and that eventual consistency is based on transparency, facts, and a well-crafted chain reaction of atomic actions. You learned how to increase team confidence by using an event hub to create an outbound bulkhead between upstream and downstream services, and how the event sourcing pattern turns events into facts by saving them in perpetuity in an event lake.
We dug into the details, and you learned how to implement fault-tolerant stream processors and optimize a subsystem’s messaging channel topology. Also, you learned how to optimize throughput with techniques such as multiplexing, pipelining, asynchronous non-blocking I/O, and sharding.
In the next chapter, we will cover the Command Query Responsibility Segregation (CQRS) pattern and see how it helps us fight data gravity, by implementing a data life cycle architecture that turns the database inside out and creates...
