The adoption of agile approaches to application delivery has fundamentally changed the way a lot of businesses now deliver solutions to end users—they roll out applications from development to production in increments that service end users much faster than ever before. The infrastructures that support these IT initiatives are far more fluid and have a self-service component that was unheard of in the past.
Previous to recent advances in technology, developers would request IT services so they could build and scale their applications in development, and then they’d request more IT services to coincide with production delivery dates. QA often took a hit as a last minute request because each IT entity operated in its own silo. This scenario was a recipe for a slow-moving, high-touch environment, prioritizing quality over speed for solid applications deeply rooted in many organizations—but often at the expense of more investment in talent and infrastructure coupled with less agility.
What if this were not the case? What if you didn’t have to choose between quality, cost, and agility?
You might recall this DevOps disruption several years ago: Moving from a client-server based application model with a Java-based “fat client” application that needed to be installed locally to a more web-based application approach that started as a “thin client” and then moved to the full features of HTML5. Web apps now mimic traditional apps of the past with a web UI that’s almost identical to a fat client, with the same right-click, drag-and-drop functionality available, without the app running locally. Innovation led to higher quality and more agility.
Today, IT initiatives aim to provide faster delivery of core applications for new business units, startups, and complementary services, such as mobile banking. While organizations still need to rely on what works—don’t fix a tire that isn’t flat—they have also found it quite reasonable to start delivering applications in continuous, smaller increments instead of using the pent up release cycle of planning and delivery associated with what many are now calling “industrial” or “traditional” IT approaches. With the right tools in place, it’s possible to deliver new quality digital services in an agile environment while keeping costs in check.
All of these initiatives can be classified as DevOps, Web-Scale IT, and Bimodal (as introduced by Gartner) and they can benefit greatly from a SaaS-based monitoring solution. Since it’s critical for organizations to support both traditional and agile modes of IT service delivery, solutions must be in place to track the status and progress of each. The success of these varied initiatives begins with an innovative monitoring approach. A SaaS monitoring solution is capable of scaling with the cloud, tracking and enabling the management of usage, provisioning resources, and providing visual insight of what’s running and who’s using which resources.
The specific benefits of a SaaS monitoring solution for each of the DevOps, Web-Scale IT, and Bimodal type initiatives include:
- All—Having total performance visibility about the health of cloud-based infrastructure enables IT to be proactive when a metric goes outside a threshold. Using a SaaS monitoring solution that scales easily with the cloud will provide a “right-fit” approach and can be self-service for many use cases.
- Web-scale IT, Bimodal—When specific business lines start accessing cloud computing infrastructure, you’ll quickly have high-level insight into end user usage patterns. You can scale up or scale down resources to meet fluid demands and be cost effective.
- DevOps, Bimodal—When infrastructure is provided as a service internally or externally for development platforms, to run new and complementary software, or to host any agile infrastructure you need, having a graphical view of all the server instances you have running, and organized by who is using them for what, can help you plan for upgrades and reprovisioning resources from one group to another as necessary.
- Web-scale IT—With real-time streaming performance data from your cloud infrastructure in large, distributed architectures, you can quickly rule out whether or not your cloud computing bandwidth is causing a bottleneck.
Today’s IT requires real-time monitoring and visibility into application response time. Watch this TrueSight Tech Short to hear a discussion with BMC experts and see a brief demonstration of TrueSight Pulse capabilities.
- Gene Kim on DevOps: DevOps Cookbook Ex. Pattern #1: Deploy in Sprint
- Implementing a release management solution in a traditional enterprise
- Continuous Delivery vs Deployment vs Integration: What’s the Difference?
- #1 My experience with introducing DevOps in a traditional enterprise
- DevOps Best Practices for Enterprise Architecture