Przeciążysz system złą decyzją | Tomasz Stolarczyk

👉 If you want to design architecture consciously, rather than just copying conference buzzwords, check out this course: https://devbites.pl/kursy/feature-fla... Have you ever looked at a system and had no idea what actually caused a given error, because events were flying around unchecked? The inability to decide when to use choreography and when to orchestrate is a sure path to cascading events and uncontrolled system overload in the most unexpected places. In this video, we break down this age-old architect's dilemma. You'll learn the hard truth: architecture isn't about choosing the "more fashionable" pattern, but about making business processes no longer default and becoming visible and measurable. This is the key to becoming a designer of resilient and understandable systems that don't explode at the first opportunity. Episode Mentor Tomasz Stolarczyk is a software architect associated with Arkency, with over 10 years of experience working with production systems. He specializes in event sourcing, CQRS, and Domain-Driven Design. He co-creates solutions used by teams around the world, including his own event store. He focuses on a pragmatic approach to architecture. Table of Contents 00:00 - Indecision leads to a cascade of events and system overload. 00:41 - Which approach is less common, but sometimes necessary? 00:49 - Choreography - high autonomy and no coordinator. 01:33 - Orchestration - Process Manager and task delegation. 02:24 - Practical example - employee onboarding in both models. 04:47 - When to use choreography? Pros and cons. 05:14 - When does orchestration save the day? (Make the implicit explicit). 05:56 - A hybrid approach - the golden mean in a bounded context. Questions answered here: 💡 Choreography or orchestration - what to choose in an event-driven architecture? 💡 How can you avoid a situation where the system becomes an unmanageable "spaghetti" of events? 💡 What is a Process Manager and why is it worth having it in your code? 💡 How to debug distributed processes using Correlation ID? 💡 Does orchestration always have to mean a Single Point of Failure? 💡 What are the risks of cascading system overload due to a lack of coordination? In this episode, you will learn: ✅ Why business processes are poorly exposed in choreography. ✅ How to embody business processes directly in code instead of guessing them. ✅ What's the difference between event subscriptions and waiting for feedback from a manager? ✅ How to design an employee onboarding flow using different contexts. ✅ When is it worth using a hybrid: choreography inside and orchestration outside modules? ✅ Why having a single place for error handling and compensation makes a developer's life easier? Check out our other materials – each one is just as informative as this one. If you liked this one, there's a high chance you'll be delighted with the next ones. We put a lot of effort into creating this content, so take advantage of it – especially since it's completely free. Also check out: ➡️ You just killed system performance! | Łukasz Reszke    • Właśnie zabiłeś wydajność systemu! | Łukas...   ➡️ CQRS step by step | Tomasz Stolarczyk    • CQRS krok po kroku | Tomasz Stolarczyk   ➡️ Contract testing as part of your strategy! | Łukasz Reszke    • Testy kontraktowe jako element strategii! ...   ➡️ Frontend without waiting for the backend – Optimistic UI | Tomasz Stolarczyk    • Frontend bez czekania na backend – Optimis...