- Synchronous, asynchronous or event-driven communications are all possible solutions. However, you need to consider the tradeoffs while deciding which form of communication would work best for your requirements.
- How does your architecture impact coupling? For instance, asynchronous communication reduces temporal coupling between services.
- Other consequences for consideration; for example, synchronous communication requires certain resilience patterns.
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.