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

Подписаться 997 тыс.

Просмотров 62 тыс.

50% 1

This presentation was recorded at GOTO EDA Day 2024. #GOTOcon #GOTOeda #GOTOldn
gotoldn.com
David Boyne - Senior Developer Advocate at AWS ‪@Boyney‬
RESOURCES
/ boyney123
/ david-boyne
www.boyney.io
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:
gotoldn.com/2024-eda-aws-day/...
RECOMMENDED BOOKS
Adam Bellemare • Building Event-Driven Microservices • amzn.to/3WfNKfM
Peter Sbarski • Serverless Architectures on AWS • amzn.to/3hJzEUM
Michael Stack • Event-Driven Architecture in Golang • amzn.to/3G5e8ST
Ford, Richards, Sadalage & Dehghani • Software Architecture: The Hard Parts • amzn.to/3v4pKQS
Gerardus Blokdyk • Event-Driven Architecture EDA • amzn.to/3FOfUHE
James Urquhart • Flow Architectures • amzn.to/3Tyz8cY
/ gotocon
/ goto-
/ goto_con
/ gotoconferences
#EDA #EDAVisuals #EventDrivenArchitecture #EventStorming #SoftwareArchitecture #AWS #EventDriven #Complexity #BoundedContext #EventDelivery #EventDesign #DavidBoyne #Serverless
Looking for a unique learning experience?
Attend the next GOTO conference near you! Get your ticket at gotopia.tech
Sign up for updates and specials at gotopia.tech/newsletter
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
ru-vid.com...

Наука

Опубликовано:

21 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 15

@daveboyne 20 дней назад

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

@jscancella 20 дней назад

hands down the best EDA summary video I have watched. Thank you for making this and sharing it with us!

@juancruzdelatorre7923 20 дней назад

Great talk! Loved your presentation style too

@daveboyne 20 дней назад

@@jscancella thanks! Glad you enjoyed it

@daveboyne 20 дней назад

@@juancruzdelatorre7923 thank you 🤘

@UptownBoogieDown 20 дней назад

A brilliant talk thank you

@MerrionGT6 20 дней назад

Good talk - thanks.

@dronicx7974 19 дней назад

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.

@shaneh3509 21 час назад

There's a lot going on here - the first thing is $, there's not an infinite budget, most companies need to get something out there so customers can try it, give their opinion, and then the companies will move to capture more of the market by reacting appropriately to that feedback (fix/build more) Start ups are generally working to find that magic "capture enough of the market to get an income" sweet spot. There's next to no point spending a lot of time/money getting something perfect that nobody wants to use/buy. Scale-ups, on the other hand, are companies that have something that the market wants, and are now dealing with having to produce a reliable/scaleable system, and that's when engineering needs to manage complexity and technical debt (and has the budget to do so)

@Tony-dp1rl 19 дней назад

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

@Cineenvenordquist 19 дней назад

No events, only Tao.

@KathySierraVideo 19 дней назад

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.