This month's Dev Breakfast is focused on Site Reliability Engineering, SRE, a way of working that implements DevOps, emphasizes reliability and automation and claims to make people happier. Read more to understand how!
Meet Pasi, this month's curator
Pasi Huttunen is a Senior Cloud Consultant at Futurice who loves technology and AWS, Azure, and GCP all alike. But what he especially loves is to see that technology is used to improve clients’ business and to serve people better. This includes both end-users and all people developing and operating said service. For that reason, he is madly in love with Site Reliability Engineering, which not only makes developers purr happily but also widens the smile of end-users and business.
Do you want to know the basics of Site Reliability Engineering and you have only 10 minutes? Then watch this video.
In this free CloudAcademy course video, Jeremy Cook does a hella good job cramming everything you need to know about SRE into a tight package: what is SRE, how it differs from DevOps, and what are the SRE's main principles and practices. From high-level to details, all aspects are covered.
Don't forget to check the other Jeremy's SRE course videos too!
A blog post that describes the differences between “traditional” outsourced ops, DevOps and SRE, written by “Yours Truly”.
Rarely do any dev or ops people think that outsourcing operations to the cheapest partner hiding behind tickets and SLAs are a good thing, but how can you try to persuade businesses to go with DevOps or SRE instead?
This blog post compares these three models and builds an understanding of how they differ and what could be the selling points that help your or client’s organization to invest for a better future and better ROI, which makes developers, end-users, and thus also business happier in the long run.
A bit longer read that delves into two paths, as the title implies: what are the SRE team topologies (there are many!) and how to heck can we get started. TL;DR Does SRE force you to separate dev and ops? Hell no!
There are many ways to implement SRE and different team topologies which suit different sized companies with different DevOps and SRE maturity. This article helps you to understand some of the typical team topologies and their pros and cons.
For example, to mention some of the topologies, there is “Embedded”, where SRE expert joins already existing DevOps service creation team to transform their way of working, or “Infrastructure”, where centralized SRE teams build enablers and foundations to help all dev/DevOps teams to not waste their time solving common cloud problems which every other team also face.
There is also a great link at the end of the article which points to “how to get started” documentation.
I know some of you readers might be like "yeah cool beans this SRE but it doesn't affect me because I am a developer".
Let’s end this journey with a tight quote.
If you are in a team that builds and operates or will operate a service or product, the latest published State of DevOps has an interesting quote for you:
“We found that the more a team employs SRE practices, the less likely its members are to experience burnout. … Teams that meet their reliability targets through the application of SRE practices report that they spend more time writing code than teams that don’t practice SRE.”
I've understood that developers love to develop, and no one loves to burn out, so this should affect you also!
If you have time to only read two pages, make them pages 19 - 20.
Most people think of Lambda when hearing Serverless. But Lambdas are literally just a tiny part in that field. Who would have thought that a tiny function goes big and become a crucial part of Software Development!
Are you allergic to doing the same things over and over again? Do you have a natural tendency to want to automate it away and make a computer do it? Do you have the computer skills to make that happen?
Futurice is seeking people who want to modernize the ops in DevOps using software development approaches and best practices. We want people who have a passion for running services in production or enabling development teams' productivity but who are tired of the repetitive manual work, brittle systems, and hiding behind tickets and want to change that for the better!
Check our job postings and join our new SRE and Cloud team!
Cloud Engineer
If you like solving client problems with coding, automation, and processes, then this role might be of your interest.
We welcome you to work with the most motivated and multi-talented people in development.
Does developing simple solutions for complex problems excite you? Then this opportunity will get you to showcase your talent and become a part of our SRE team.