Software architecture for a rapidly changing world – with Barry O’Reilly

Podcast Notes

Residuality Theory — in very few words — is a method of designing software architectures inspired by how the most talented architects do it: i.e. starting from the stress conditions that the system could eventually face as it operates.

Barry O’Reilly is a software architect with 25 years of experience in the IT industry. He has held leading roles at global software companies and has spent many years educating architects he is currently pursuing a Ph.D. in Complexity Science and Software Engineering at The Open University.

Residuality theory looks at the world not as a bunch of static things or still pictures, but as a constantly moving set of processes that we can’t really see and grasp. It requires designers to move away from a static view of the system: by letting the architecture design be inspired by its “stressors”, O’Reilly thinks that not only can we design more resilient systems but also more efficient ones.

In this episode, Barry also describes the philosophical background behind the theory and why Residuality can be a viable approach to designing organizations too.

Key highlights

• Static representation of reality as a practice of software architecture is embedded in Western philosophy and worldview
• Software engineers should ask themselves: “What is the underlying philosophy behind what I do and the frameworks I use?”
• Residuality is a way to look at the world as a constantly shifting, moving set of processes that we can’t really see and grasp
• The residue is what remains from the system after it breaks down: it’s the leftover of the system. And those leftovers will define the future of the software system
• Criticality as an indication of the system’s ability to function across a wide range of attractors, which we may or may not even know about
• It is known that software performing well in its environment is modular, but how to make structured decisions around such modularity remains unknown
• The impossibility to separate organizational design from software architecture

Topics (chapters):

(00:00) Barry’s quote

(00:59) Introduction

(02:12) What residuality theory is

(12:59) Residuality: philosophical background.

(18:24) Residuality: from software to organizations.

(27:01) Residuality and microservices: is a match possible?

(36:13) Is residuality fit for the society we’re living in, or is it a next-generation thing?

(43:03) How to (easily) adopt a residuality approach

(48:48) Barry’s breadcrumbs.

Recorded on 22 February 2023.

Get in touch with Boundaryless:

Find out more about the show and the research at Boundaryless at https://boundaryless.io/resources/podcast

• Twitter: https://twitter.com/boundaryless_
• Website: https://boundaryless.io/contacts
• LinkedIn: https://www.linkedin.com/company/boundaryless-pdt-3eo

Music:

Music from Liosound / Walter Mobilio. Find his portfolio here: https://blss.io/Podcast-Music