Event Driven Architecture - Understanding the Basics

In this video, we will discuss what is Event-Driven Architecture and we will understand the basics of EDA from a complete architectural perspective.

Content
0:00 - Introduction
0:33 - Classical Monolith Architecture
1:23 - Microservice Architectures
5:00 - Event-Driven Architecture
6:40 - Event-Driven Architecture designing
7:33 - Apache Kafka
8:20 - Events
9:19 - Understanding Events
10:58 - Event Streaming
11:36 - Producer/Consumer of Events
13:55 - Real Event-Driven Architecture app (.NET)

#eventdriven #eventdrivenarchitecture #executeautomation #eda
For more articles and videos, please follow
► [Twitter] @executeauto
► [Subscribe] @Execute Automation

New Series 2021
#############

Selenium and C#
******************

Selenium &Java
******************

CI/CD with Microsoft Technologies
*************************************

Docker & Kubernetes
************************

Mobile Testing
****************

[Bozo---]

One thing not well explained in the video is that we should keep in mind that events are sent after the work is done. Or for long running process you can have an event saying processing and another one done (but even here you would probably use a queue). But in most of cases events mean something changed, the subcriber is not the one doing the work, it is doing extra work afterwards. You want the subscriber to read consistent data. (ex. a database)

[bottle_money]

such a well explained video. only after watching this have i understood the difference between microservice and event driven architecture. extremely clear explanations. thanks for the video

[swtestacademy]

DJ Karthik on air! Starting from 06:43 😃👍🏻

[myprojectideas]

You speak really well. Thanks for the video.

[vinayakpatil]

Nice, clear and simple explanation. Well done.

[vijaybabaria]

Clarifies lot of high level things, thanks

[jatinaneja]

Hi...Well explained....Which tool did you used to create arch diagrams?

[felipecastrorichter]

Thank you! It was a great explanation I learned a lot from this😁

[lugojenkins]

Great video, thanks for the good explanation!

[chigozieG]

You did a great job explaining, thank you!

[afnanalam]

Thank you sir, very well explanation.. can you tell me which extension are you using in VS code?

[sainiranjan]

Thank you very much for another great video, Karthik
Does memory has any impact while the event is sitting on the topic of the kafka forever ?

[felipecastrorichter]

Is the tell/get pattern also known as the pub/sub pattern? Or are they different?

[lobster]

Hey great video, quick question though. If the app/UI is always listening for events to be published, would that also mean that it will have to maintain a open websocket connection with the api? If so, wont this architecture require a open stateful connection for every connected client? Thinking of the increased infrastructure costs with this architecture, if any. Thanks

[sharathkumar]

Hi Karthik, Very well explained. Event driven architecture results in "Eventual consistency", so automating at API level becomes challenging at times. So far I used retry to overcome these flaky tests. Any suggestions from your side Karthik.

[queenstownswords]

Hello Karthik, good video. I hope you are well in level 4. I have built a test strategy on a few micro-service orgs now and I am curious what your take is (given the example in this video).

[KircaTurka]

Hi buddy! Thank you for this. What about the data storage, where does that go? So mobile number change event is captured but what where is the mobile number history kept? I.e. at point 1 it was 1234 and was updated to 2345 and so someone can report on the history of the mobile number?

[AmNotLegend]

if an event not interested by any services, what happens? does it block other events in theQ to be handled by the consumer?

[LazyShady]

wouldn't the producer going down be a single point of failure?

[willl]

Is like putting a program that you didn't design as the heart of your app