Allen Holub

Architecture (of both your code and your organization) and process are interrelated and interdependent. Change one and you must change them all. Agile transformations fail when the code and organizational structure don't change to make agility possible. A new software architecture will fail if your organizational architecture doesn't change to support it. In this lecture, you'll learn: • How architecture, process, and organizational structure interact and why. • How Agile principles and values influence software and organizational architecture. • What an agile-friendly architecture looks like and how to create one."

A big-up-font design is a sure way to build the wrong thing. We learn as we work, and the things we learn impact our architecture. In a modern, agile, world we design systems incrementally as the system evolves rather than in one giant up-front phase. We design incrementally as we build. Nonetheless, our designs must still be coherent and able to easily stand up to the stress of changing requirements. This philosophy is particularly true in the microservice and Agile worlds. This practical workshop shows you how to design a system that can evolve incrementally. You'll learn: • the simplicity principle—build the simplest thing that does the job. • several architectural patterns appropriate for incremental development • how to create strictly-isolated highly decoupled subsystems • domain-focused architectures (including DDD) • how to use the domain to get system coherence over time • how to identify key abstractions, bounded contexts, entities, aggregates. • how to use events and messaging instead of declarative interfaces and APIs • event storming as both an analysis and design tool In all, you'll learn how to build a coherent and highly maintainable system and architecture that can easily accommodate changing requirements and grow incrementally as the system evolves.