Skip to content

Commit

Permalink
Add link to DevOps Finland talk blog page from original blog
Browse files Browse the repository at this point in the history
  • Loading branch information
CaroleK committed May 24, 2024
1 parent fa7050a commit 332767c
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions posts/demystifying-service-level-acronyms.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,8 @@ featured: true

In this fundamental level blog post I will explain what different Service Level concepts mean and how to use them effectively in the software delivery process.

I also did a talk at DevOps Finland on this topic, [Service Levels, Error budgets, and why your dev teams should care.](https://verifa.io/blog/service-levels-error-budgets-devops-finland-talk/)

## What is a Service Level and why does it matter?

Depending on the source, I have seen claims that anywhere from 40% to a [whopping 90% of a software systems lifetime costs](https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3610582/) consist of operational and maintenance costs, making the development costs of the software pale in comparison. [Additionally, costs of even short service breaks and unplanned downtime are significant](https://assets.new.siemens.com/siemens/assets/api/uuid:3d606495-dbe0-43e4-80b1-d04e27ada920/dics-b10153-00-7600truecostofdowntime2022-144.pdf) and getting more expensive still. This goes to show that being able to maintain your service availability and preferably being able to preemptively react to service degradation is not just a matter of convenience, but carries a very real price tag with business consequences.
Expand Down Expand Up @@ -81,4 +83,7 @@ When building and serving software you care both about evolving it, but also abo

Using Service Level Agreements, Objectives and Indicators and Error Budgets effectively in your software development process enables you to strike the right balance between change versus stability. They define common goals to your developers and operations, promoting co-operation and data-driven decision making. They give your teams more ownership and agenda over the products they build and make it easier to react to problems before they can take effect.

I also did a talk at DevOps Finland on this topic, [Service Levels, Error budgets, and why your dev teams should care.](https://verifa.io/blog/service-levels-error-budgets-devops-finland-talk/)


If you need help optimising your software development and continuous delivery processes, don’t hesitate to [get in contact with us!](https://verifa.io/contact/)

0 comments on commit 332767c

Please sign in to comment.