Overview
Syllabus
intro
preamble
eda
james eastham
you learn much more in failure than you do in success
aim for low coupling and high cohesion
why be event-driven?
what does it mean to be event-driven?
events are first class citizens... ?
event carried state transfer
evolvability - a core feature of event-driven architecture
now what?
governance
so, fat vs sparse events?
embrace the metadata / data pattern
asynchronous - what happens when you think async?
embrace eventual consistency
observability - what happens when things break?
boundaries - surely you need synchronous sometimes?
start small
thank you for listening
Taught by
Conf42