The Cloud Native approach to operations.

Change is inevitable. To keep up with it, your organisation's codebase needs to be  sustainable, and you need to make all the tweaks you need to make, safely, and for the lifespan of your product. 

That's where SRE can help. 

SRE—or Site Reliability Engineering—started as a set of practices at Google and is being adopted by more companies all the time to help them stay competitive and retain IT talent. (At Container Solutions, we use its principles as the basis of our 24/7 Customer Reliability Engineering, or CRE, service.) 

To learn more about SRE, fill out the form provided to request your free e-book.




You should know by now that we wouldn't give you an e-book full of fluff. No one's got time for that nonsense. Here's what this one will give you: 

  • What SRE is, and why you might need it.
  • The connection between SRE and Cloud Native
  • The differences between SRE and DevOps
  • What SLIs, SLOs, and SLAs are and the roles they play in SRE
  • Patterns for following best practices for SRE

Meet the author

Michael (1)

Michael Mueller is Chief Customer Officer at Container Solutions. Michael oversees the architecture and implementation of Cloud Native systems for organisations from every sector. His work spans two decades in various roles, with current emphasis on SRE, automation and Cloud Native in general. He enjoys solving the challenges presented by emerging technology and working with partners. Michael is also a CNCF ambassador spreading the Cloud Native word.