Event Driven Architecture - Understanding the Basics
HTML-код
- Опубликовано: 30 июл 2024
- 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
► [ExecuteAutomation] executeautomation.com
► [Twitter] @executeauto
► [Subscribe] @Execute Automation
► [Udemy] www.udemy.com/user/karthik-kk/
New Series 2021
#############
► [Microservice Development] • Developing Microservic...
► [XUnit with Selenium] • XUnit with Selenium
► [Git Basics] • Git Basics - Everyday ...
► [SpringBoot for Testing] • Spring Boot for Automa...
Selenium and C#
******************
► [C# for automation testing] • C# for Automation Testing
► [Selenium with C#] • Introduction to Seleni...
► [BDD with Specflow] • BDD and Specflow
► [BDD with Selenium] • BDD with Selenium and ...
► [Selenium .NET Core] • Playlist
Selenium &Java
******************
► [Cucumber with Selenium] • Section 1 - Cucumber w...
► [Cucumber with Selenium] • Section 2 - Cucumber W...
► [Cucumber 4 Upgrade] • Section 3 - Upgrade to...
► [Selenium Grid] • Selenium Grid
► [Selenium framework development] • Selenium Framework Des...
► [Selenium 4] • Selenium 4
► [Selenium Grid with Docker] • Selenium Grid with Docker
► [Puppeteer] • Puppeteer
► [E2E with Cypress] • Cypress Tidbits
CI/CD with Microsoft Technologies
*************************************
► [Azure DevOps Service] • Azure DevOps Service 2019
► [Automated Build deployment] • Automated Build+Deploy...
► [Build + Deploy + Test with Jenkins] • Build+Deploy+Test with...
Docker & Kubernetes
************************
► [Understanding ABC of Docker] • Understanding ABC of D...
► [Understanding Docker for Windows] • Understanding Docker f...
► [Selenium Grid with Docker] • Selenium Grid with Docker
► [Kubernetes for Testers] • Kubernetes for Testers
Mobile Testing
****************
► [Understanding Appium] • Introduction to Appium...
► [Appium with C#] • Introduction to Appium...
► [Appium with Java] • Setting stage ready fo...
► [Appium with C# (Advanced)] • Introduction to Appium...
► [Appium Framework development] • Introduction to appium...
► [Mobile Automation testing with Xamarin.UITesting] • Part 1 - Introduction ...
► [Android automation with Robotium] • Part1 - Introduction t...
► [Flutter app automation with Flutter Driver] • Part 1 - Introduction,...
► [TestProject] • TestProject (Basic)
► [Katalon Studio] • Katalon Studio
► [WinAppDriver] • Windows Application Dr...
► [Angular Automation] • Angular automation wit...
► [EAWeekly] • Playlist
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
You did a great job explaining, thank you!
Nice, clear and simple explanation. Well done.
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)
Great video, thanks for the good explanation!
Thank you! It was a great explanation I learned a lot from this😁
Thank you for a great explaination.
Clarifies lot of high level things, thanks
You speak really well. Thanks for the video.
Nice one thx. Straight to the point.
Really great video! Thanks bro
DJ Karthik on air! Starting from 06:43 😃👍🏻
Very well explained
Great video😊
great explanation
Great video
Thanks for the video
Thank you sir, very well explanation.. can you tell me which extension are you using in VS code?
Thank you!
Very good video 👍
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 ?
Awesome
Let's always do alot of good ❤️
Hi...Well explained....Which tool did you used to create arch diagrams?
Is the tell/get pattern also known as the pub/sub pattern? Or are they different?
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
Yes, and these connections can be stored in a service that maps the customer id to the web socket session, using the event bus to initiate messages back to the client via web sockets. Everything is abstracts into these event reactive services so everything can scale, but not for maximum efficiency or even speed.
Very well explained
👍🏻
wonderful explanation
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?
It’s all going to be stored in your service DB with before and after event in topic(both old and new number)
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.
Hi Sharath,
The best way to test the application is to test from the consumer of the event rather than the producer itself. Producer testing will make once again the classical thinking of testing the non-event driven APIs, other way will solve the problem
Thanks,
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).
Hi Mate, Yes L4 is hard, but keeping safe so far ! Hope you are doing safe too.
Actually, I am planning to create an application on EDA using .NET and also wanted to explain how to test the same. This way, it will be even more better to understand.
But to your question, the best way to test is to test the consumer rather the producer itself.
if an event not interested by any services, what happens? does it block other events in theQ to be handled by the consumer?
Not at all, it will just sit there and expires
@@ExecuteAutomation is this a Queue? consumer polling from head or tail. if an event on head or tail, not consumed, the events behind will have to wait until the one on the top to be consumed?
@@AmNotLegend yes, but it’s event streaming queue using Kafka or RabbitMQ. It’s not like stuck there until someone consume, if so, there is no point in having this used by multiple services
Is like putting a program that you didn't design as the heart of your app
wouldn't the producer going down be a single point of failure?