InfoQ Homepage Evolutionary Design Content on InfoQ
News
RSS Feed-
Patterns of Legacy Displacement - Thoughtworks Summarizes IT Landscape Evolution
Martin Fowler recently published a series of articles called Patterns of Legacy Displacement. It summarises the authors’ collective experience in replacing legacy systems. They argue that chances of success are increased by dividing such projects into three phases and following the patterns listed for each one.
-
Modular Monolithic Architecture, Microservices and Architectural Drivers
Kamil Grzybek thinks that too often we implement a microservices architecture because we believe it will solve all problems in a monolithic application. Instead, we should focus on architectural drivers to find the best architecture for a system. In a series of articles, he has started to describe the basic concepts of a modular monolith and the drivers leading to a specific architecture.
-
The Swift Method: A Framework for Software Modernization Using DDD
The Swift Method is a set of techniques for analyzing complex legacy systems, and determining the work required to gradually modernize key components or the whole system.
-
How Technical Practices Support Evolutionary Architecture and Continuous Delivery
Technical practices of XP such as TDD, Refactoring, CI and Pair Programming support emergent design and enable evolving your architecture. The first practice you need for continuous delivery is CI, committing to mainline every day. Being able to write clean, well-factored, and well-tested modular code is the most important skill for developers.
-
Characteristics of Evolutionary Architectures
The first principle of Evolutionary architecture is support for incremental non-breaking changes. Microservices architecture is one great example of such an architecture, Rebecca Parsons and Neal Ford from Thoughtworks claims when describing characteristics and principles of Evolutionary architectures.