Infrastructure architecture and the similarities to software

Wed, 06 Feb 2008 11:41:23 GMT

I've just finished working on a review of the infrastructure architecture behind a number of fairly large media websites. Infrastructure isn't really my speciality¹, but what I found interesting about this piece of work was the number of direct comparisons that can be made with software architecture.

This particular environment had a group of thinkers (the architects) and a group of do'ers (the team looking after the infrastructure boxes). As with many software projects, the architect team have become detached from the day to day reality of the infrastructure and see their job as predominantly forward facing. For example, they look at new technology and how the infrastructure can be modified in the future, leaving the do'ers to get their hands dirty with the day to day operational aspects. This reminds me of ivory tower software architects dictating technology decisions to developers without truly understanding the nitty-gritty of the real-world requirements. It's the type of situation in which I can see the hand-off taking place.

One of the complexities with this particular environment stems from the fact that the do'ers are actually split into multiple teams, with each team representing a different part of the architecture. While this isn't necessarily bad, the problem is that there is no single technical authority; be it a single person or a team with wide representation. With a lack of clearly defined technical authority, each team works within their own silo and, as with many software projects, inconsistencies evolve.

In summary then, ivory towers aren't unique to software architecture and although somebody needs to own the coherent vision, they also need to be aware of the day to day problems that are being solved in the real-world.

¹ thankfully I had a good team of SMEs with me; I naively just assume that the network people will wire my boxes up in the right way :-)

The non-coding architect

Mon, 02 Jul 2007 19:14:00 GMT

I found a great blog entry today by Frank Kelly called How to spot the dreaded non-coding architect (NCA), which is about some of the differences between architects that can code and architects that can't (or don't). Since this site is about "coding the architecture", I thought you might find it interesting too.

These NCA folks can be really quite dangerous and give dev teams a bad name ... But how can you spot one? For most developers it's pretty easy but just in case you can't I've compiled a list of example scenarios that should help - comparing the often dogmatic attitude of the NCA with the pragmatism of the experienced Coding Architect (CA).

Recommended reading and a little humour to brighten up your Monday.

Coding the Architecture - ivorytower tag

Infrastructure architecture and the similarities to software

The non-coding architect