you learn much more in failure than you do in success
6
aim for low coupling and high cohesion
7
why be event-driven?
8
what does it mean to be event-driven?
9
events are first class citizens... ?
10
event carried state transfer
11
evolvability - a core feature of event-driven architecture
12
now what?
13
governance
14
so, fat vs sparse events?
15
embrace the metadata / data pattern
16
asynchronous - what happens when you think async?
17
embrace eventual consistency
18
observability - what happens when things break?
19
boundaries - surely you need synchronous sometimes?
20
start small
21
thank you for listening
Description:
Save Big on Coursera Plus. 7,000+ courses at $160 off. Limited Time Only!
Grab it
Explore the fundamentals and intricacies of building event-driven systems in this comprehensive conference talk from Conf42 Cloud Native 2024. Delve into key concepts such as low coupling, high cohesion, and the benefits of event-driven architecture. Learn about event carried state transfer, evolvability, and governance in event-driven systems. Discover the pros and cons of fat versus sparse events, the importance of embracing metadata and asynchronous thinking, and the role of eventual consistency. Gain insights on observability, setting boundaries, and starting small when implementing event-driven architectures. This 35-minute presentation covers essential topics for developers and architects looking to leverage event-driven design in their cloud-native applications.
Building Event-Driven Systems: Principles, Challenges, and Best Practices