Architecture. The Hard Parts by Neal Ford

Architects often look harried and worried because they have no clean, easy decisions: everything is an awful tradeoff.
Architecture has lots of difficult problems, which this talk highlights by investigating what makes architecture so hard. At the core of many architectural problems: getting good granularity, which we illustrate via event-driven architectures, teams, components, architectural quantum, and a host of other examples.
We also illustrate reuse at the application, department, and enterprise level, and why reuse seems simple but isn’t. We also discuss difficult decisions, how to do tradeoff analysis, tools like MECE lists, and how to decouple services to achieve proper granularity.
Architecture is full of hard parts; by tracing the common reasons and applying lessons more universally, we can make it softer.
www.thoughtworks.com/

[@SOMM_Work]

One of the must-study resources on the path to becoming a distributed architecture expert.

[@manju4ever222]

I'm currently an Architect at Lowe's. This is truly a gem i was waiting for.

[@rprates]

Great content, thank you for sharing

[@sat849]

Thanks for sharing

[@sirim7052]

Great explanation. Thanks for this amazing video. I have a question about parallel saga. How is Error handling managed in case of parallel saga ?

[@sinusmd]

does async calls implies always a message queue ?

[@forsakensandor]

No