
By Aruna Ravichandran | Article Rating: |
|
April 19, 2016 01:00 AM EDT | Reads: |
905 |

Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important - because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators.
But new code doesn't just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performance, cost, reliability, and scalability. For developers to write code that behaves well, they need great cloud APM.
What Cloud APM Tells Cloud Developers
Most people think almost exclusively about what cloud APM tells cloud ops teams. After all, those ops teams need APM tools that empower them to quickly pinpoint performance bottlenecks and the root causes of application outages. With the right APM tools, cloud ops teams can rapidly resolve - and even proactively prevent - capacity issues that can adversely impact the user/customer experience.
Ops teams, however, don't modify code. They have to live with what developers produce. If code is written inefficiently, ops has no choice but to add provisioning as necessary to meet service-level objectives.
Developers, on the other hand, can fix bad code behaviors. The right cloud APM technology can tell them exactly what those behaviors are. In fact, the insights provided by APM tools are indispensable to any development team charged with writing excellent code.
Cloud APM, in other words, is the feedback loop that cloud developers need to ensure that DevOps is not only functionally Agile but also operationally excellent.
Completing the DevOps Loop
Of course, completing the cloud DevOps loop requires more than just a good APM tool. You also need processes that capture the problematic code behaviors discovered via APM and feed them into your software change management environment. These processes should include:
- Clearly itemized code behavior issues. It's not enough just to tell developers their code is somehow inefficient. They need hard data on specific issues. Is a middleware workload getting triggered with surprising frequency? Are too many database threads being opened - while too few get closed? These specifics are essential for ensuring that developers apply their skills in ways that actually deliver value.
- Well-managed issue prioritization/triage. A core aspect of Agile development is smart control of scope. In keeping with this scope control, DevOps teams need to make sure they appropriately prioritize code behavior issues based on how they impact cost and user experience.
- Issue accountability. Once developers work on a code behavior issue, it's essential to monitor the results. Those results cumulatively drive learning that makes the whole process more effective and efficient - whether it's developers learning how to write better-behaving code or DevOps managers learning that some of the issues they tend to flag aren't code-related at all.
Organizations that leverage cloud APM in this way will significantly improve the quality and consistency of their end-user experience, while also achieving non-trivial reductions in cloud costs. Proactive attention to code behaviors also substantially mitigates the business risks associated with full-scale service outages.
For these reasons and more, every IT organization bent on cloud excellence should make cloud APM an integral component of their DevOps environment.
Published April 19, 2016 Reads 905
Copyright © 2016 SYS-CON Media, Inc. — All Rights Reserved.
Syndicated stories and blog feeds, all rights reserved by the author.
More Stories By Aruna Ravichandran
Aruna Ravichandran is the VP of Marketing, Application Performance Management and DevOps at CA Technologies.
![]() Apr. 19, 2016 08:45 PM EDT Reads: 1,717 |
By Elizabeth White ![]() Apr. 19, 2016 08:45 PM EDT Reads: 1,063 |
By Pat Romanski ![]() Apr. 19, 2016 08:00 PM EDT Reads: 615 |
By Liz McMillan ![]() Apr. 19, 2016 08:00 PM EDT Reads: 295 |
By Elizabeth White ![]() Apr. 19, 2016 08:00 PM EDT Reads: 884 |
By Elizabeth White Apr. 19, 2016 08:00 PM EDT Reads: 869 |
By Liz McMillan ![]() Apr. 19, 2016 07:45 PM EDT Reads: 883 |
By Elizabeth White ![]() Apr. 19, 2016 07:15 PM EDT Reads: 274 |
By Liz McMillan ![]() Apr. 19, 2016 07:00 PM EDT Reads: 1,278 |
By Elizabeth White ![]() Apr. 19, 2016 06:45 PM EDT Reads: 2,027 |
By Liz McMillan ![]() Apr. 19, 2016 06:00 PM EDT Reads: 1,038 |
By Elizabeth White ![]() Apr. 19, 2016 05:45 PM EDT Reads: 1,063 |
By Elizabeth White ![]() Apr. 19, 2016 05:45 PM EDT Reads: 651 |
By Liz McMillan ![]() Apr. 19, 2016 05:45 PM EDT Reads: 713 |
By Pat Romanski ![]() Apr. 19, 2016 05:45 PM EDT Reads: 653 |
By Elizabeth White ![]() Apr. 19, 2016 05:15 PM EDT Reads: 1,339 |
By Elizabeth White ![]() Apr. 19, 2016 05:15 PM EDT Reads: 1,711 |
By Pat Romanski ![]() Apr. 19, 2016 05:00 PM EDT Reads: 1,770 |
By Pat Romanski ![]() Apr. 19, 2016 05:00 PM EDT Reads: 1,449 |
By Carmen Gonzalez ![]() Apr. 19, 2016 04:30 PM EDT Reads: 2,494 |