Audience
Anyone involved in a software innovation process.
Key-Learnings
- The basics of Site Reliability Engineering (SRE)
- SRE is different for every organisation
- How to apply SRE in an organisation already far on the DevOps journey
Why a mature DevOps organisation will benefit from applying Site Reliability Engineering
As the scale of development has grown in the last two decades, the industry has come to realise that separating development and operations is not a scalable way to manage innovation and software systems.
Google has been developing their brand of DevOps since around 2000 and that has turned into what is now known as Site Reliability Engineering.
At bol.com (Innovation department of about 700 people) we’ve been “Doing” DevOps for at least 4-5 years now. Why then do we now need a full-time central SRE team?
Learn all about the state of bol.com’s SRE journey and why you might want to get one underway as well.