By their very design, monolithic architectures make it incredibly easy to implement atomic operations, isolate different threads and guarantee consistency of data.
Unfortunately, with modern distributed systems the same rules can’t (and don’t) apply.
This means you are in charge of dealing with consistency yourself.
- What inherent problems exists in managing consistency with microservices
- The three basic strategies for consistency problems (ignore, apologize, or resolve)
- Why your approach to solving inconsistencies depends on the business need
- How to take on consistency challenges with a workflow engine
Co-Founder and Chief Technologist, Camunda
Bernd Ruecker Co-Founder and Chief Technologist of Camunda, author of "Practical Process Automation", and co-author of "Real-Life BPMN", is a software developer at heart who has been innovating process automation deployed in highly scalable and agile environments of industry leaders such as T-Mobile, Lufthansa, ING and Atlassian. He contributed to various open-source workflow engines for more than 15 years, and is constantly discussing new process automation paradigms that fit into modern architectures around distributed systems, microservices, domain-driven design and event-driven architecture.