Sand Castles and DevOps at Scale
by Niall Crawford
A Bit of History
The phrase DevOps first appeared back in 2008 at an agile conference in Toronto. And in a nutshell (& courtesy of Wikipedia) can be defined as a software engineering culture and practice that aims at unifying software development (Dev) and software operation (Ops). Ultimately with the intent of reducing the time between committing a change to a system and the change being placed into normal production, while ensuring high quality.
Well, that’s the theory at least, and to be fair “mileage” somewhat varies.
+ The success of DevOps is invariably dependent on the quality of the individuals & the team.
And in my opinion, the biggest challenge in most organizations (particularly the larger ones) is few changes touch an individual system. In fact, it is probably quite the contrary, typically an IT change impacts many systems, processes & services and crosses many technology teams, divisions, and various IT Environment tiers e.g. applications, data & infrastructure tiers.
+ In today’s complex IT environments, few systems or components are islands.
And here lies in the issue.
+ DevOps encourages a culture of “System” or “Team Thinking”.
However, effective DevOps at-scale requires us to think at a broader “Enterprise” level.
An Analogy: DevOps & DevOps at Scale
+ It is a little bit like comparing the building of Sand Castles on a Beach to Town Planning.
Yes, it might be fun & you might build a damn good sandcastle (or CICD capability) but unfortunately, some of your sister teams will fall short of the mark, and ultimately the whole task of integrating is going to slow down and the so-called “Release Train” will grind to a sudden halt.
Delivering DevOps at Scale
Organizations cannot expect DevOps teams, which are naturally focused on discrete systems or atomic tasks, to effectively manage and deliver a solution at scale unless there is some form of enterprise harness that ensures all the moving parts can be effectively orchestrated.
+ DevOps is more than simple Code, Build, Test, Package, Release, Configure & Monitor.
Ultimately, DevOps at Scale is about resolving the classical cross-system orchestration challenges experienced today and providing an approach, preferably a complimentary & non-obtrusive approach, that overarches existing DevOps methods and ensure the release train wheels are greased and your delivery is streamlined.
As a way of preparing for a DevOps at scale capability, here are five practices to promote.
- Understand what your End-to-End Environments look like.
Look beyond your systems & model the End to End IT & Test Environments they live in. Understand them intrinsically i.e. map your components, dependencies, interfaces, business relationships, processes and supporting operations.
- Shift your release / operational planning & coordination left
Avoid the ongoing issues around System not being fit for purpose and/or contention. Capture project & portfolio demand as early as possible and establish effective notification & transparency methods to ensure readiness and awareness.
- Don’t neglect the data
How often do you see the CICD solutions fail as nobody bothered about the data?
In addition to streamlining Application & Infrastructure tasks, invest in data. Automate key data tasks like ETL (Extract, Transform & Load) and/or Fabrication and ensure the automation methods are “cross system aware”, thus ensuring E2E integrity.
- Orchestrate enterprise release activity
Avoid common “release issues”, “deployment delays” and “rollbacks” by adopting an “Enterprise Release Management” (ERM) strategy. A strategy that promotes prioritisation of change, alignment of cross-system release activities and promotes consistent and repeatable operations.
- Promote higher levels of “Enterprise Intelligence”
System metrics are fine although off little use to executive decision makers or your CIO. Start capturing & reporting on “Enterprise Metrics” i.e. metrics that allow the senior executives to see the “forest from the trees”. Examples may include Team Performance, Compliance, Automation & Innovation
Enov8 provides a complete platform for addressing organisations DevOps at scale requirements. Providing advanced “out of the box” IT & Test Environment Management and Release Management capabilities, the enov8 platform uplifts enterprise transparency, command and ultimately control.
Innovate with Enov8
If you are interested in learning more about IT & Test Environment Management and IT Release Management, contact us about EcoSystem.
EcoSystem is a fully configurable and easily integratable solution that comes with out of the box “enterprise management” functions that support IT & Test Environment Management, Release Management, Data Management, IT Operations Management, Configuration Management & Service Management.
Niall is the Co-Founder and CIO of Enov8. He has 25 years of experience working across the IT industry from Software Engineering, Architecture, IT & Test Environment Management and Executive Leadership. Niall has worked with, and advised, many global organisations covering verticals like Banking, Defence, Telecom and Information Technology Services.
19 MARCH, 2020 by Michiel Mulders SRE vs DevOps: Friends or Foes? Nowadays, there’s a lack of clarity about the difference between site reliability engineering (SRE) and development and operations (DevOps). There’s definitely an overlap between the roles, even though...
06 MARCH, 2020 by Arnab Roy Chowdhury Top 10 SRE Practices Do you know what the key to a successful website is? Well, you’re probably going to say that it’s quality coding. However, today, there’s one more aspect that we should consider. That’s reliability. There are...
20 FEBRUARY, 2020 by Arnab Row Chowdhury Technically, the world today has advanced to a level we never could’ve imagined a few years ago. What do you think made it possible? We now understand complexities. And how do you think that became possible? Literacy! Since...
14 FEBRUARY, 2020 by Michiel Mulders A site reliability engineer loves optimizing inefficient processes but also needs coding skills. He or she must have a deep understanding of the software to optimize processes. Therefore, we can say an SRE contributes directly to...
07 February, 2020 by Arnab Roy Chowdhury Do you remember what Uncle Ben said to young Peter Parker? “With great power comes great responsibility.” The same applies to companies. At present, businesses hold a huge amount of data—not only the data of a company but also...
17 JANUARY, 2020 by Sylvia Fronczak Site reliability engineering (SRE) uses techniques and approaches from software engineering to tackle reliability problems with a team’s operations and a site’s infrastructure. Knowing the history of SRE and understanding which...