In this video, we are going to talk about event driven microservices architectures.
Basically advantage of Microsoft's architectures is means communicating with microservices via event
messages.
We said that we wanted an architectures.
We can do asynchronous behavior and lose the coupled services.
In example, instead of sending the request when data needed, services consume them via events.
This provide to performance increases.
But also there are huge innovations on the event driven microservice architectures, like using real
time message platforms, stream processing, even tops, real time processing, batch processing, data,
intelligence and so on.
So let me recap what is event driven architecture?
Basically, we use events when implementing our use cases.
For example, for our E commerce application, we have a few microservices like customer order payment
and products and we have several use cases across microservices like a customer creates an order with
some products and if the payment is successful, the products should be delivered to the customer.
This is one of the use cases, right?
So we can perform the whole process with events and event is more understandable for customers also.
So that could be a flow of events like a customer creates an order, the customer receives a payment
request.
If the payment is successful, the stock is updated and the order is delivered.
If the payment is not successful, roll back the order and set the order status is not completed.
So this is more human readable and if any business requirement appears, it is easier to change the
flow.
This is also a very good match.
The microservices and communications microservices will only care about the events, not about the other
microservices.
They process only events and publish any event to trigger other services.
This approach is traditional approach for event driven architectures.
But we can make this event driven approach is more generic and real time event processing feature.
With evolving this architectures.
There are huge innovations on the Microsoft's architectures.
As we said before, real time message platform, stream processing events, ups and so on.
Please see this image.
According to this live event with Microsoft's architecture, everything is communicating via event.
We Can Think Event Up is a huge event store database that can make real time processing.
As you can see that every microservices, applications, Iot device even function as a service server
services can interact with each other with subscribing events in event hub.
Also, these event upstream data can process by big data.
Tools like Apache Spark also can apply to machine learning pipelines for generating recommendation service
like recommend the best next offer for our ecommerce application.
So this is the event of microservice architecture.
In the next video we will see application integration pattern for microservices.