What is Event Driven Architecture (EDA)?
HTML-код
- Опубликовано: 2 окт 2024
- Explore IBM Event Automation → ibm.biz/IBM_Ev...
Check out IBM Cloud Pak for Integration → ibm.biz/cloud-p...
Check out IBM Garage for Cloud Event-Driven Reference Architecture → ibm.biz/garage-...
What is an event-driven architecture, or EDA? And how does it enable real-time user interactions, pluggable microservices, and extensible streaming and data analytics?
In this lightboard video, Whitney Lee from IBM Cloud, visually breaks down the answers to these questions and many more, as well as explains the several advantages and opportunities that an event driven architecture provides for developers and organizations in comparison to a request/response application architecture.
Learn more about EDA → ibm.biz/eda-guide
Learn more about FaaS → ibm.biz/guide-t...
Learn more about Serverless → ibm.biz/learn-a...
Get started on IBM Cloud at no cost → ibm.biz/create-...
Subscribe to the IBM Cloud channel to be notified when a new video drops → ibm.biz/subscri...
#EDA #FaaS #Serverless
Looking at the First 20 Seconds and asking myself: What is with that lightning setup?
Wondering the same. Why is there only heads and hands in the video 😂
Love this series. Understanding so much in so little time about fundamental concepts.
Thanks for all of the great content lately.
This is no good, she never completed a single "example". Is never answered a Q what EDA is really stands for. Ended up being about specific technology - kafka :(
IBM you're so good at explaining concepts with these videos. I remember watching one on the difference between an API and an SDK some time back and it was very helpful. I now understand that the event backbone is the most important part of the system. I guess other services can subscribe to it(either to all its events or just to some events that it receives) and process the event data however they want. Thanks for an awesome video
The presenter shared a few use cases. I like the presenter to finish the check-out use case first before jumping on the music streaming. How do you handle distributed transaction of the check-out flow in the event-driven architecture? If the user cancels his transaction, for example, there should be a compensating message. How about duplicate events published? Idempotent consumers are required to de-duplicate the message. I think EDA is hard and complicated, it's not what the presenter said it's so easier. You mentioned Kubernetes at the beginning, what is it to do with EDA? Eventual consistency shall be discussed when using EDA. etc. Thank you for the knowledge sharing.
Curious to know how you are able to do that mirror thing. 🤔
Simple. The image is flipped/mirrored in post-production. In other words the presenter is right-handed.
They use a lightboard, www.lightboard.info/
Had the same question 😂
ruclips.net/video/wCOuu0-o5YI/видео.html
That's a lot of code waiting for app and API developers to write. That's a lot of logging to sanitize and onboard to the backbone. That's a lot of data streams for admins to understand and write actionable if - then statements. That's a lot of reporting for owners and perf engis to sift through. There's a lot of IT professionals working hard to ensure this kind of infrastructure for multiple sources of data and systems scale appropriately. Hire good people to run good systems and you're winning.
Its quite easy to understand, please make more such videos
This is great content. Better explanation of Event Driven designs
Thank you and love to overview and the clear/concise explanation. You're teaching style really shines.
I feel like this class can only be understood by people who already know this stuff. Its a whole lot of names and acronyms without enough explanation of what they're meant for. Like event backbone for example. 7 mins in still there's no moment of clarity I was hoping for.
First of all, great video. I like the prensentation format, but i'm still a little bit confused about two (probably more, haha) things. I'm just learning about architectures, so excuse me, if my questions seem obvious:
- 1.) Let's start with the roboter vacuum cleaner. I'm having trouble understanding the flow of data and corresponding actions being taken. The roboter sends an event to the event backbone (a kind of server I assume), which triggers a FaaS, which takes action "with the vacuum cleaner" eg. cleaning the house? How is that achieved? Does the robot have to have a connection to be able to clean?
- 2.) Store case: A customer triggering a checkout event, which updates the inventory seems logical. But how about responses to user specific data. E.g. denying the checkout because of an empty inventory or a payment (verification) event, which only corresponds to one specific order. Same thing can be asked about the spotify play event, which triggers the "suggestions" process. Who handles sending the song data to the client or the suggestions, which only apply to a users currently hearing that song.
I would be glad if someone could sacrifice some time and offer their insight. Thanks!
Simple yet concise!
Aspiring, thanks for the great content, keep it up!!!
wait a second, is she… WRITING BACKWARDS????.????
I wonder if this is how alchemists in the 18th century felt when they summoned a demon and a disembodied torso appeared out of the darkness and then started them teaching the secrets of the universe
"Statement of fact": almost 30 years ago, Sybase databases (dont know about others) kept writing something that was called "transaction log". That e.g. made it easy to implement replication. Transaction log is about logging all data manipulation. Statement of fact. Every single sql-statement executed.
I mean, what's the big difference ? --- And the answer is: messaging: publish and subscribe.
Curious to know how it will work in below scenario.
Ton of people checking out a same product which is for sale for short amount of time on retail website.
Because there will be lot of rush plus it has to let other services know immediately since that product will be out of stock in few minutes.
How in EDA above case will be handled? I believe this is a lazy architecture, meaning one doesn't get response immediately it takes time but will surely respond. I think such principle won't pan out in above scenario. Can you shed some light on it?
Each order is a wish. They are then either accepted or rejected by inventory and an event is sent to indicate what happened.
So if multiple events arrive, some are accepted, and some are rejected, usually dependent on queue position.
Very nice explanations. I am very impressed that she writes through a glass so that we can read it ...
the video is flipped horizontally. i had the same thought
thank you very much, I like IBM company
Good talk. Terrible audio quality (it's constantly clipping).
is she writing in opposite direction?
Thank you women with floating hand☺
I was studying EDA in 1970. When is IBM gonna make a EDA computer for real?
It's great, in starting I found everything is bounced off, but later got a crystal clear understanding. Thanks for making it simple & clear. One question comes to mind what are the other architecture, can you name them...!!!
Thanks for watching, Mishra!
Regarding other types of software architecture, which EDA is an example of, there are MANY! 🙂
Some of the most talked about today, based on different uses and patterns are: N-tier architecture, microservices, service-oriented architecture, and event-driven architecture, of course.
You can start on some of them here: ibm.co/3iDSA5o
Going even further, there's the Cloud Architecture center: ibm.co/3xqmNJD
Are you all hiring a production team that realizes awkwardly cast shadows DURING the shoot, so that they can be mitigated? If so, call me!
Good vid. But its legit a 12 minute description. If your going to watch this, you need to watch all 12 minutes, thoroughly
This channel should feature on Netflix
Why don't you write everything beforehand and just go over your slides quicker 😂😂
she writes backwards so we understand that is something i have not seen before, normally the board is behind
How these animations are created ?
Stand in behind the glass, mirror the camera, if she's using some kind of highliter then maybe some blacklight too.
faas usually last onle few mins. on this example a msg queue should be important
What is the difference between extensible and scalable
thanks ...
The checkout example is one of the worst usecases chosen for event driven systems. An order has to be coordinated, consumers would need to sync because an order has to act like a distributed transaction/saga. If you would implement it like described in the video the customers will be contacted the shipping left warehouse, but the product was not even on stock! The order has to be done in sequential steps which can fail or get canceled, by having a queue system you will lose the ability to do so, and each consumer will react async in both time and space.
Stream history is one of the biggest challenges in an EDA / microservice architecture. Not all services start their existence at the same time. Or even worse: You want to integrate legacy systems with events originating from them - but they didn't produce events from the beginning of their life. So it's much easier to talk about an EDA-based system if you just see the present. But how do you make sure every (new) consumer has seen all the data it needs - originating from events?
I was wondering the same. I was thinking one would have to prime system B with an scoped and extracted view of system A events.
EventStore and replayable events.
Had to pause cuz for the first minute I was just wondering how did she write mirror.
Terrible audio quality.
How do you ensure that only a single worker instance processes a given event, when your use case requires exactly-once handling? Is it based on Kafka's partitioning of topics? Or perhaps some sort of distributed lock built on e.g. zookeeper? Or maybe some sort of cyclical leader election with failover capability on node heartbeat loss?
You are correct in your first suggested solution. Most often, we rely on Kafka's exactly-once guarantees that comes by way of it's guaranteed ordering of events in a single topic partition, idempotent producers, and transaction-enabled producers and consumers. Leveraging the Kafka Exacty-Once Semantics that has been around for a few years and has been hardened in recent releases allows us to build low-overhead event-streaming applications with processing guarantees.
Can't see anything written on the board.
Wow, how did you manage to record this, it looks like you are behind the Glass, and writing the letter in reverse.
Hey there! We shared some backstage "secrets" of our videos on the Community page, check it out here 👉 ibm.co/3zgLZnl 😉
@@IBMTechnology Thanks for sharing :)
There's something about using terms in this video that I do not fully understand. In the introduction the presenter shows that message driven is one of the key points to achieve scalability and resiliency. But then, it shows that that's achieved with an event driven architecture and not a message driven one.
very informative video, thank you very much
That was creepy
Is event backbone volatile or persistent storage? please explain the event backbone in detail.
So Cloud Software Developer or Customer Success Manager?
Hello, I am looking for an internship. Is there any opportunity ??
She is a great lecturer! Respect.
Could somebody switch on the light?
Wait timeout lol she's standing behind glass, looking at the camera right on the other side right? She writes her letters backwards really well lol just noticed that!
Search on "lightboard videos"
@@IBMTechnology The X-FIles: Season 1, Episode 4, 43:36
I think you should be more stick with one scenarios when you are explaining such concept. you were on shipping and then you start explaining ... robot cleaner.
Thanks so much
Super helpful
does the lecturer write in reverse ? that's awesome
See ibm.biz/write-backwards
Its more event sourcing than event driven arch.
Wait. Is she writing backwards?
It's filmed through a glass pane and the image reversed in post-production.
Isn't the background too dark?
😘 Thank for your knowledge.
Really nice explanation
Great content 👍
Thank you 🙌
You are awesome! thank you!!
Do you really need send a message to Shipping on Checkout? Should be when user click on Order Confirm
The scenario here is an exemplar and one that could be refined through deep-dives and discovery, as needed. Deriving a business scenario to implement using event-driven architectures is usually done through an Event Storming Workshop. That would then help to establish all the actors, all the actor interactions, and the necessary data to flow through the system. In this example, sending a message to Shipping on Checkout is a simple way to show an extensible system and evolutionary architecture - exactly what EDA was made for.
One of the best, clear and concise introduction i found.
this is an irrelevant question but still.. is she writing backwards or is it some tool\trick?
writing on glass between her and the camera, then mirroring the video afterwards
wonderfully done... please share which app u are using to create the animations
Distributed system != kubernetes. Get out there of here with that
Thankyou for making things simpler to understand ❤️
Thank you so much for the content! Great stuff!
these videos are so good to get into hard topics
I enjoyed your presentation, and I learned useful tips. Thank you :)
Very informative.
Thank you for this video
Really really good content! :)
Is the straight line connected automatically by program or it is post-processing?
The animation of checkout is amazing, what is the technology behind this?
Scanning IBM Tech Videos be like ''AI ... skip ... AI ... skip ... AI ... skip ... EDA ... finally, something useful, Play"
Perfect
Awesome video!
Glad you enjoyed it, Nicolas! 🙂
Thanks a lot. The content was so valuable.
We're glad you found it useful! 👍
Hah since when does scaleable mean k8n. That's like saying mobile communication means iPhones.
Amazing presentation, thanks for this class!
Thank you for watching! 🙂
Very good content. Simple yet informative and to the point. I have one question is , event driven architecture is shift from normal request response scenario or architecture. How user interaction or UI component handle in this event driven architecture?
You looked like some ghost with black + black setup 😬😬
very very basic.
holy crap! was she writing backwards?