In its DevOps 2021 survey of global IT professionals, Enterprise Management Associates (EMA) found that 95% of organizations with highly successful DevOps initiatives were predominantly decentralized and purposefully becoming more so as fast as possible (see Figure 1).
This decentralization of development and DevOps teams is making site reliability engineering (SRE) both critical and difficult to achieve.
Figure 1: Current organizational models. Source: EMA
Site reliability defined
Site reliability crosses domains running the enterprise gamut from code to customer and everywhere in between. Developers code new applications and features. DevOps speeds those innovations into production. IT operations keeps the infrastructure and systems running.
Theoretically, they all work together to deliver great service to employees and customers alike. Unfortunately, human nature undercuts that theory: When something is everyone’s business and no one’s job, it doesn’t always get done.
When done right, however, and laser-focused on IT service reliability, SRE asks and answers these questions:
This question-and-response cycle is iterative and endless, always moving in the direction of improved reliability through automation.
The automation connection
The modern drive to automation is increasingly paired with advances in AIOps. Recent EMA research found that AIOps and automation—although technically distinct sets of technologies—are inextricably linked in organizations that are highly successful in their AIOps initiatives. Not surprisingly, those organizations also report:
When asked to rate the top three capabilities most important in an AIOps solution, SRE groups selected:
All of these attributes require the unifying reach of a platform to create visibility of applications, services, and microservices across the enterprise.
Powered by enterprise-spanning platform technology and practices, enterprise SRE exerts a multiplier effect on individual team productivity. Decentralized IT teams are transformed into efficient parts of a unified organizational whole, with no disruption to their autonomy, speed, or effectiveness.
Benefits of SRE adoption
SRE adoption provides a business-defined balance of IT innovation at speed and scale with service reliability and cost. In addition, it offers numerous other predictable benefits and outcomes:
The people connection
As always, the catch is people. Enterprise SRE requires a paradigm shift in how IT operations works with the rest of the enterprise world. It’s a recalibration from break/fix to optimization. Although it’s a change that benefits all stakeholders, it’s nonetheless a change.
Economies of scale and the advantages of artificial intelligence (AI), ML, and innovative human initiatives such as enterprise SRE cannot be achieved in fenced-off domains of independence. Cross-domain thinking, cooperation, organization, and practices have to precede cross-domain processes and automation.
Consider starting with modernization of your incident handling processes. This practical integration can be relatively painless and return high value for the effort. Service management and operations both benefit when IT leverages AI/ML to automate incident and event handling processes.
Learn more in our Enterprise SRE: service reliability ebook.
ServiceNow, the ServiceNow logo, Now, and other ServiceNow marks are trademarks and/or registered trademarks of ServiceNow, Inc. in the United States and/or other countries. Other company names, product names, and logos may be trademarks of the respective companies with which they are associated.