This will be a slight departure from my usual posts about random bits of code and have more a focus on architecture.
In the last few years the world of development has seen quite a bit of upheaval as it adapts to new ways of working, the devops movement has, when implemented well, proven incredibly effective in increasing ‘throughput’ of code as well as offering opportunities for team empowerment and increased stability of the final product. Unfortunately, that ‘when implemented well’ is sometimes a sticking point. The idea behind devops is too integrate development and operations, to make operations (ie: deployments, infrastructure) more code driven and automated. What happens when it’s implemented badly though is that a separate ‘devops’ team is setup within an organisation, the majority of the members being sysadmins with maybe one guy who knows how to write bash scripts. I’ll cover devops in more depth in another post, but what I want to focus on in this post is the move towards software defined architectures, and how that movement can be harnessed effectively.