Complexity is the Gotcha of Event-driven Architecture • David Boyne • GOTO 2024

This presentation was recorded at GOTO EDA Day 2024. #GOTOcon #GOTOeda #GOTOldn

David Boyne - Senior Developer Advocate at AWS @Boyney

RESOURCES

ABSTRACT
Organizations today face significant challenges in adapting quickly to technological advancements and shifting consumer demands. This struggle often leads to decreased innovation and agility, hindering business growth and competitiveness.

Event-driven architecture (EDA) offers a powerful solution that extends beyond the traditional roles of producers, consumers, and brokers. It facilitates the creation of dynamic architectures that evolve, empower teams, and enhance agility, enabling businesses to thrive in rapidly changing environments.

This talk delves into how complexity can obscure the potential of event-driven architecture (EDA). We'll investigate how EDA contributes to the growth of evolutionary architectures and discuss the guardrails and governance strategies needed to manage complexity and fully harness EDA's potential.

Whether you're improving your current architecture or embarking on a new journey, this session will offer actionable insights into controlling complexity and help you realize the potential of event-driven architectures. [...]

TIMECODES
00:00 Intro
05:08 Agenda
05:41 Potential of EDA
21:03 Guardrails to manage complexity
37:58 Biggest gotcha of them all
45:04 Summary
46:30 Outro

Read the full abstract here:

RECOMMENDED BOOKS

#EDA #EDAVisuals #EventDrivenArchitecture #EventStorming #SoftwareArchitecture #AWS #EventDriven #Complexity #BoundedContext #EventDelivery #EventDesign #DavidBoyne #Serverless

Looking for a unique learning experience?

SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.

[daveboyne]

Thanks for the opportunity to talk, was a great day ♥️

[dronicx]

What a very insightful talk. It's crazy that with the overwhelming amount of evidence that suggests that people should manage complexity as soon as possible, especially in distributed systems which most projects are, many software companies still force their devs to manage complexity after MVP release or very close to it. From my experience, these people always believe that rushing bad MVPs fast is better because being first to market is more important. I don't think these companies understand that being first doesn't matter if the codebase is unmaintainable after a year from MVP release due to extremely bad decisions from everyone involved. There's a reason unicorn companies are not profitable and would literally not exist if they didn't receive millions in funding from investors believing the same lie. Software engineering is a profession for people that can do trade off analysis, and most people managing software engineers can't do this and don't allow their software engineers to do their trade off analysis and actually use that as input into their development, which is why we end up with clusterf*cks of codebases even in EDA projects.

[stevenhe]

Haha rediscovering the 30-year old Erlang.

[Tony-dprl]

Event Catalog is a pretty good little tool. Does a good job of filling a niche well

[KathySierraVideo]

We have the teeny Farm-Maxx mini round baler, and we love it. A small horse farm with a small tractor and a 7+ acre hay field. It’s too hard for us to manage the bigger bales, so we mostly had to buy square bales each year. By saving thousands of dollars not buying hay, we were able to justify the purchase of the baler and a Tedder/rake. The bale size is perfect for me to move around by hand, and store in smaller barns and sheds, without needing a tractor to move the bales.