While you might have used REST as your service communications layer in the past, more and more projects are moving to an event-driven architecture. Let’s dive into the pros and cons of this popular architecture, some of the key design choices it entails, and common anti-patterns. By Jason Skowronski.
The article delivers on:
- What is event-driven microservice architecture?
- Why use event-driven architecture
- When to use REST
- Your most important design choice – messaging framework
Your basic choice comes down to message processing or stream processing.
Of course, event-driven architectures have drawbacks as well. They are easy to over-engineer by separating concerns that might be simpler when closely coupled; can require a significant upfront investment; and often result in additional complexity in infrastructure, service contracts or schemas, polyglot build systems, and dependency graphs. Good read!
[Read More]