Last week, during the @buddygit webinar, I had the pleasure to talk with @filiptepper about Site reliability engineering. What is it, who needs it, and what do we need to learn to work in SRE?
A thread š§µ
What is SRE? This term was created by Google, but based on a company we work at it sometimes means something different.
In general, it's a culture of collaboration between software engineers and system operators to bring scalable and reliable software.
The term that really interested me was "blameless debrief" - it means that if an accident occurs the team concentrates on the accident itself rather than on the person who caused it.
It's all about the WHY it happened rather than WHO caused this.
Who should implement SRE? Everyone.
The good news is that you don't the team for that to start with. You can start just by implementing the methodology. When you'll grow, you'll see more and more benefits of it.
One of the key aspects of SRE is observability. It's key to have your application provide you constantly with all the data that can help you fix bugs if an error occurs or even prevent them.
What do you need to know to become a Site Reliability Engineer? A bit of everything from the software engineering and system ops worlds.
If you want to watch the whole webinar head to youtube.com/watch?v=R33UoHWVUqo
Also, don't forget to subscribe to our YouTube channel to get informed about all the upcoming webinars.