Reg readers on: Stuff you run vs stuff you run it on
Workshop Thanks to everyone who took part in our latest mini-poll, which teased out some insights on how you balance the requirements of the teams that build and operate the resources and capabilities running in the server room.
On the face of it, the overall relationship between software developers / procurement and those tasked with running applications appears quite healthy (figure 1). In fact, 60 per cent of you fell into the three camps that we could argue are the most desirable in terms of striking a balance between requirements and capabilities – and only 25 per cent felt that application workloads were built with scant regard for operations. So far so good.
Let's focus on what drives the requirements on how applications are managed? Our Reg reader poll proved to be a pretty broad sample. The SLA merchants roughly balance with the ‘ad hoc basis’ players; and IT practitioners ‘flying by the seat of their pants’ matched those who managed their applications on an individual basis.
How do the approaches fare when it comes to taking a call on their effectiveness? Interestingly there are few marked differences between the SLA (service level agreement), ‘manage everything’ and on ‘each app’s merit’ approaches. We can see that formal SLAs do not guarantee the most effective management of software applications – but perhaps this doesn’t matter, apart from that with an SLA you know when something went wrong.
Clearly, there is little between adopting a more ad-hoc approach and flying completely blind. The former group may be fooling themselves, but it’s amusing to see that ‘flying blind’ attracted more ‘5’ scores than ‘informally trying to maintain pace with the businesses needs’ did. We know who you are.
When we dig down into the data (not shown) and cross match the approaches with specific problems encountered, we do see the expected differences - that the SLA guys lead the way, but not always by much margin, and the pant-seat flyers generally lag in all categories. But beyond that it’s a mixed-up bag, and we couldn’t really pull out any trends strong enough to report back on.
Overall, we picked up acknowledgement of the opportunity improvement in quite a few areas - User skills and training came out on top. Does lack of training lead to actual application management issues beyond stressing the help desk with password reset requests? We’d love to know more about that.
Ultimately, from what we can glean from such a short poll, the balance between requirements and resources seems to be in good shape for most of you. Sure, we know from recent projects that often there are serious implications of the practice of ‘develop and hope’ when it comes to operational resilience, but given the horror stories we’ve heard from you in other areas, this all looks relatively sensible. Which is a bit of a result.
Sponsored: DevOps and continuous delivery