Software is constantly changing, which makes flexibility one of the fundamental qualities of good software architecture. In our latest interview, Eberhard Wolff, initiator of the CPSA-Advanced Level Module FLEX – Flexible Architecture Models and today a supporter of its curator team, explains what makes an architecture truly flexible and why this requires looking beyond individual architectural styles such as microservices.
FLEX takes a holistic approach to flexible architecture, combining ideas from Domain-Driven Design with different architectural approaches, including microservices, moduliths, and monoliths. A central challenge is finding the right way to divide domain logic into modules. Eberhard also emphasizes that architectural decisions influence much more than technology: system boundaries affect team structures, responsibilities, and collaboration, making flexible architecture relevant far beyond the role of the software architect.
Key Takeaways
Flexibility is a fundamental quality of software architecture.
Software is designed to change over time. An architecture that can accommodate this change therefore creates significant long-term value.
Flexible architecture is about more than microservices.
Microservices provide certain forms of flexibility, but they also introduce additional technical complexity and costs. FLEX explores alternatives such as moduliths and monoliths and incorporates lessons learned from real-world microservice architectures.
Finding the right boundaries is one of the biggest challenges.
How domain logic is divided into modules has a major impact on the flexibility of a system. According to Eberhard, this is a common architectural challenge for which many practitioners still lack a clear understanding.
Flexible architecture involves more than technical roles.
Architectural boundaries can influence how teams are structured and what their responsibilities are. This makes the topic relevant not only for software architects and engineers, but also for product owners, managers, and others involved in shaping software systems.
AI can support architecture work, but architecture remains a people business.
LLMs and AI can be additional tools for supporting architectural decisions, but they do not replace the shared understanding needed among the people and roles involved in designing a system.
Want to learn more? Watch the full interview with Eberhard Wolff below and discover how the FLEX module helps professionals understand the principles behind flexible architectures and design software systems that are ready for change.