DevOps and SRE
Step into the cultural movements that of DevOps and SRE to more quickly deliver reliable and healthy software solutions.
- 6 Topics
- 8 Replies
In the linked blog post, posted just today, Google Cloud has announced that they are modifying the pricing structure for Managed Service for Prometheus. The modifications include the addition of a new tier for those with massive utilization of the service, along with reduction in pricing for every tier available.https://cloud.google.com/blog/products/devops-sre/managed-service-for-prometheus-offers-new-pricing-tierMonitoring and providing clear visibility into your systems is an essential element of DevOps and SRE workloads. Prometheus is a powerful tool to provide that, but can get challenging to maintain in a performant, resilient, consistent manner across widely distributed workloads. Google Cloud’s Managed Service for Prometheus takes the burden of managing and scaling your Prometheus datastore off of your teams so they can focus on using the data instead of on collecting and storing it. Are you using Managed Service for Prometheus? How much of a savings will your team realize from
What are SLOs?Service level objectives (SLOs) are part of a set of measures to increase the quality of service management. This set of instructions helps to understand which behaviors really matter, how to measure them and how to evaluate them so that the service has an acceptable quality. SLOs are key to making data-driven decisions about reliability. They are at the core of SRE practices. This brings greater confidence to the Site Reliability Engineering (SRE) team about what is important for the full functioning of the service, as well as resulting in a positive end-user experience. Why SREs Need SLOs?Site Reliability Engineers cannot manage their services correctly if they have not identified the behaviors most important to the service and to customers. Carefully considered SLOs prioritize the work of SRE teams by providing data points that allow leaders to consider the opportunity cost of performing reliability work versus investing in functionality that will gain or retain cus
Shared Benefits of DevOps and SREWith the growing complexity of application development, organizations are increasingly adopting methodologies that enable reliable, scalable software. For over a decade, two similar concepts, DevOps and SRE, have been existing together in the world of software development. They may look like competitors. However, a closer view reveals that obvious rivals are complementary pieces of a puzzle that fit nicely together. DevOps is a broad philosophy and culture because it affects more major changes than SRE does. DevOps is more context-sensitive. DevOps is relatively silent on how to run operations at a detailed level. Site Reliability Engineering (SRE), on the other hand, relatively defined responsibilities. Its remit is generally service-oriented and ends user-oriented rather than the completely business oriented.This chapter from the book "The Site Reliability Workbook" explains how DevOps and SRE facilitate building reliable software, where they overlap
The following article was posted on the Google Cloud Devops-SRE blog and provides advice for SRE teams around choosing their SLOs appropriately. I especially appreciate two components of this blog post. First, the emphasis on visibility into your system when assessing appropriate SLOs, and second, the use of visibility and risk analysis in the process.Have you been responsible for identifying SLOs for your systems? Did you use a systemic analysis of risk as recommended by this article? Did you consider the impact on visibility into system performance if the services you use for monitoring and alerting fail?https://cloud.google.com/blog/products/devops-sre/how-sres-analyze-risks-to-evaluate-slos
State of DevOps 2021 report (from Google Cloud’s DevOps Research and Assessment - DORA - team) is available at the following link: https://cloud.google.com/devops and has some really interesting takeaways.One of my favorites? The recognition that SRE and DevOps are complimentary cultures! For a while I was seeing a lot of posts on LinkedIn and elsewhere asking whether you thought DevOps or SRE was a stronger methodology, and I always thought the question was odd. In my mind they have always been complimentary. Both highly responsive, focused on keeping the customer happy by meeting their needs rapidly, incorporating as much automation as possible, and relying upon agile teams…What’s your favorite takeaway from the report? Share here in a comment!
I know cloud is the future, I have recently started getting certified in cloud, I have got certified in some azure fundamentals. I have plans to get certified in GCP too , but waiting for a opportunity like this one :) Recently I came to know that C2C is big GCP community. The event was very interesting, Keeping your business websites up online is a great hard work and knowing how the team SREs do this 24×7 is indeed interesting.I have already heard about SRE online, but I wasn't sure what really does a SRE do in daily job. This event helped me to know more about SRE.Some interesting points:- 2500 SREs are behind google systems.- Have multiple versions of your apps for availability.In the event I asked a question to Alexis about what would happen if we run out of error budget.Finally I didn't do networking with other attendees, but I am free to connect and discuss. :)Thanks for great webinar.
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.