Laying a foundation for dynamic software architectures

The label 'dynamic software architecture' is an oft-overused seldom justified term... but does in fact denote a software system with a higher degree of moveable, changeable, adjustable components at its base layer.


There are a lot of jargon-heavy terms used in technology. All too often we find that these snappy phrases, expressions and labels are peppered into what amounts to be statements amounting to not very much at all. Dynamic architecture is one of those terms.

"We've built a software solution with a truly dynamic architecture that is ground-breaking, state-of-the-art and industry-leading," said… well, any tech marketing catalogue you care to pick up.

What the company should have said if we could turn on 'honest subtitles' is that the software system in question is open to a few updates, patches and maintenance upgrades from time to time. That's not a dynamic software architecture.

So what software architecture is truly dynamic, how can C-suite managers be sure that they're working towards achieving one in their IT function and to what extent does dynamism also come with an additional responsibility for due care and attention?

Bricks and mortar

Let's go back to basics and use a real world (albeit slightly futuristic) example of bricks and mortar. Buildings are not that dynamic; they obviously stand as predominantly static structures. But architect-futurists are envisioning a time when tower blocks have moveable floors and struts that adapt to the natural elements such as wind, rain and temperature.

To continue reading this article register now