A SkillsCast for this session is not available.
Architecture plans in enterprises tend to resemble late-night infomercials. First, you see a person or system that seems incapable of survival—a situation that can be immediately rectified if you just buy into the product. (One popular infomercial shows incompetent people mangling tomatoes transitioning into Ginsu-wielding sous chefs; the architecture pitch starts with hideous complexity then moves to clean orthogonal box diagrams.) Operators are always standing by.
Real architecture never reaches that blissful end state. Something always interrupts the program: businesses change, technology changes, or funding dries up. What would happen if you did reach the end state, anyway? Is IT in the company done? Of course not.
The truth is that there is no end state. We must all learn to build systems that evolve and grow. We need to stop aiming for the end state and understand that change is continuous. We cannot predict the details, but we can learn the general patterns.
Michael Nygard demonstrates how to design and architect systems that admit change—bending and flexing through time. Using a blend of information architecture, technical architecture, and some process change, Michael walks you through examples of rigid systems to show how to transform them into more maneuverable architecture.
YOU MAY ALSO LIKE:
- The Killer C's: Coupling, Cohesion, and Complexity (SkillsCast recorded in November 2021)
- Rust Forum (Online Conference on 24th May 2022)
- Bazel eXchange: Watch Party (in London on 21st June 2022)
- LDN Talks May 2022 - Quickwit Takeover (in London on 30th May 2022)
- Rust Macros: The What, Why, and How (SkillsCast recorded in May 2022)
- Using Scenarios to Reinvigorate Your Microservice Architecture (SkillsCast recorded in April 2022)