Slashdot Mirror
Dev vs. Ops: The State of Accountability (overops.com)
Here's an analysis by OverOps on how shared accountability affects the delivery of reliable software in a DevOps environment, and what are some of the top challenges teams face when it comes to building and maintaining quality applications. Conclusion from the report [PDF], which relies on a survey of over 2,000 IT professionals around the globe : At the center of this DevOps adoption chaos is the evolving relationship between development and operations. Many organizations are already taking a shared approach to accountability for application health, however they still lack the tools and application visibility needed to know who is ultimately responsible for addressing and fixing each issue. As the lines between these two teams continue to blur, organizations will need to focus on adopting tools that deepen visibility into their applications. Clarifying ownership of applications and services, and avoiding the "multiple owners = no owner" syndrome is a crucial for even the most bleeding edge organizations.
The "Dev vs. Ops: State of Accountability" survey revealed that as more organizations begin the transition to DevOps workflows, defining roles and processes becomes more difficult and more important. Furthermore, businesses of all sizes are building and releasing new code and application features faster than ever before, which adds additional pressure across the entire software delivery supply chain. Organizations going through the DevOps transformation are more likely to face visibility challenges that make it difficult to maintain or improve application quality and reliability.
The "Dev vs. Ops: State of Accountability" survey revealed that as more organizations begin the transition to DevOps workflows, defining roles and processes becomes more difficult and more important. Furthermore, businesses of all sizes are building and releasing new code and application features faster than ever before, which adds additional pressure across the entire software delivery supply chain. Organizations going through the DevOps transformation are more likely to face visibility challenges that make it difficult to maintain or improve application quality and reliability.
You sound like you're referring to corporate IT throughout your comment, or at least that's my impression. DevOps concepts don't really apply there...or at best it's a square peg in a round hole situation.
Building custom software, and more specifically SaaS, truly do have a lot to gain by adopting DevOps, especially when combined with Agile development.
Docker is getting more and more heavy weight, i.e. becoming full blown VMs (Though in the strict sense of the word they always were). Now part of the problem I see is that projects end up with containers scattered around like jack straws, like the "DLL hell" many experienced in the past, or plug-in hell. All docker does is allow the complexity to take a different form. Also stateless containers in my experience are pretty useless. Working on back end "heavy lifting" applications somewhere you need to maintain state and Docker and stateless containers, by definition, cannot do that.
Cloud is just putting the application somewhere else and paying by the cpu cycle. No different than before, it just makes it opaque as to what is going on and who is responsible. There's really not much new under the sun and good ideas are basically reinvented over time. Mainframe == cloud hosted apps on your mobi or browser. Nothing to see here, move along...
putting the 'B' in LGBTQ+