What is Event Driven Architecture_ (EDA - part 1) - YouTube

%% date:: [[2022-09-09]] %% # [[What is Event Driven Architecture_ (EDA - part 1) - YouTube]] Creator:: A Dev' Story URL:: https://www.youtube.com/watch?v=DQ5Cbt8DQbM ## [1:03](https://www.youtube.com/?yinotetimestamp=63) Events and messages are really referring to the same thing. ## [1:37](https://www.youtube.com/?yinotetimestamp=97) Events are IMMUTABLE. ## [2:31](https://www.youtube.com/?yinotetimestamp=151) Event-driven architecture has three components: - Producer - Broker - Consumer ## [5:12](https://www.youtube.com/?yinotetimestamp=312) Disadvantages of event-driven architecture: 1. performance - it introduces an intermediary. ## [5:23](https://www.youtube.com/?yinotetimestamp=323) 2. eventual consistency ## [5:37](https://www.youtube.com/?yinotetimestamp=337) Events can get out of sync if there are multiple services, all reading from/writing to the same event broker. ## [6:08](https://www.youtube.com/?yinotetimestamp=368) When should you use event-driven architectures? 1. When scalability is more important than performance. ## [6:40](https://www.youtube.com/?yinotetimestamp=400) Basically when decoupling the systems from the messages themselves is really important. ``` [^adevstory]: A Dev' Story. (2021). _What is event driven architecture? (EDA - part 1)_. Retrieved from https://www.youtube.com/watch?v=DQ5Cbt8DQbM . ```