What are Event-Driven Architectures? Why they are important for distributed applications?

Event-driven architecture is an architecture style that uses events and asynchronous communication to loosely couple an application’s components. Event-driven architectures can help you boost agility and build reliable, scalable applications. This is very important when building distributed and serverless applications.

In this video, you will learn what event-driven architectures are, what problems they solve, and what are the main components and will get you ready for the following videos in this series where we look at different patterns.

#foobar #serverless

☆☆ FOLLOW ME ONLINE ☆☆

📷 Instagram: foobar_codes

☆☆ ABOUT FOOBAR ☆☆
In this channel, you can find mostly coding tutorials related to cloud and serverless.
In addition, I like also talking about architecture, software design, motivation, and leadership.
There is a new video every Tuesday, so stay tuned :)

[jpablonov]

Justo en el trabajo estamos empezando a trabajar con event driven asi que me viene genial todo el contenido que estas generando. Muchas gracias, Marcia!.

[raminzandvakili]

Thank you for your videos. Would you please make a video about the difference between event and REST?

[dinoac]

Can you talk about eventual consistency common pitfalls and how to pitch these ideas to other people?

[Roy-boqe]

Great topic!!!!
It would be nice if you cover about database transaction between multiple micro services.
For example, For an event we want update two decoupled services in Event driven architecture. What will happen on a service update failed after retry also. How can we rollback other service update?
Handle through saga patterns or some other way.

[marioshobbyhq]

It would be nice to also explore how EDA impacts public APIs, which are usually synchronous and must handle the "eventual consistency" of the backend system. For example, my mobile client may call a rest API for placing an order and this will trigger some vent choreography / orchestration inside the backend, that may span some time. In the meanwhile I can't answer the client "All good, your order has been successfully processed" but I have to answer something like "Request accepted. Check the result later on." - and probably provide APIs to che ci the status of the request. For example, an API endpoint for polling the status or by publishing public events (which are part of the public API as the Rest API) through something like websockets. Or maybe use a graphql API and deal with this bidirectionality in the communication ...

[cristinaoctavian]

What the best practice if a micro-service needs to get data from another micro-service ?

[dinoac]

❤️ Marcia. Siempre creando contenido de lo que necesito. Estoy diseñando e implementando una arquitectura de eventos siguiendo en gran parte las ideas que John Gillbert propone como systems wide CQRS y event sourcing, autonomous service pattern. Me parecen ideas muy atractivas aunque el libro esta mal escrito.
Looking forward to this series ❤️❤️❤️🇦🇷

[alerodang]

Buenas Marcia, sería muy interesante ver contenido sobre iot en tu canal. Especialmente sería interesante como crear websockets con este servicio para nuestras aplicaciones sls.