Episode 166: Living Architectures with John Wiegand

Change Management

Managing architectural changes is crucial for adapting to new requirements in software systems. John Wiegand emphasizes the importance of evolving system architectures, especially in open and adaptable environments. He encourages developers to think about how these evolving systems can be applied in their own areas, suggesting that traditional architectural thoughts may not suffice for these dynamic systems 1.

If you're in a constrained problem, traditional thoughts on architectures makes full sense, but when you think about these open, adaptable, evolving systems, hopefully we triggered some thoughts for people to absorb.

--- John Wiegand

Using the Eclipse and Jazz projects as examples, John illustrates how fundamental architectures can be designed to accommodate change, focusing on plugins and linked data as core components 2.

   

API Design

RESTful API design plays a pivotal role in supporting system evolution and integration capabilities. John discusses the significance of well-defined interfaces, even within a RESTful framework, to ensure that systems remain loosely coupled and adaptable 3. He highlights the shift towards data-centric design, where the focus is on understanding and manipulating data rather than just the tools used to process it.

The importance of having a good interface applies just as well.

--- John Wiegand

This approach contrasts with traditional object-oriented programming, where behavior and APIs were prioritized over data. John notes that in modern architectures, data is increasingly becoming the central focus, with tools serving to manipulate and analyze it 4.