Member-only story
What is Event-Driven Architecture? Why Do We Need and choose it?
In this article, I’m going to be trying to explain the meaning of event-driven architecture and why we need it. I hope it will be helpful for you.
The core purpose of event-driven architecture (EDA) is a software design pattern that has a system of loosely coupled microservices that is used event-based, both the many events are being published by the system and these events are being consumed by their subscribers.
There are many features that are independent of each other in the application. Some of them are significant and vital, and some of them are just only features. Some of them are gotten a bunch of requests at the same time, and some of them are also less. Why not should we separate these running of independent features from each other? This way provides us that it is easy to maintain, develop and many independently scalable applications. That would be better, wouldn’t it? This is a statement of why we need and choose it.
What are events?
Let’s first clarify the differences between the two terms events and message. The meaning of message is actually a request from one system to another systems that included payload all the required properties of the data to be processed. For this reason, there are different types of messages. In fact, communicating among of a lot of systems can be done with events, query, commands.
As I said, event is a kind of message. This message describes what is currently happening in the system. Nobody can change or reject these events. Let’s imagine that we have many different applications and each of these is talking each other.
- service1: look, order is coming.
- service2: I took order, but you will take the money.
- service3: don’t worry, I’m going to take money.
- ……. (how many events you have)
Here is to communicate with events.
