How about we break something? We keep building and fixing everything. It's so terribly boring.
Let's break it in a way that we won't get in trouble for it — in fact, we'll even get praised for this mess. Then we'll build everything anew — and do it so much better, more resilient, and faster.
And let's break it again.
Do you think this is a competition for using the secret tool of our cosmonautics — the Big Russian Space Hammer?
No, this is an online SRE intensive. It just so happens that each course is never the same as the previous one. Simply because you can never guess what in the huge complex system, to which thousands and thousands of users connect every second, and which has an audience of millions, might drop, break, slow down, glitch, or in hundreds of other ways ruin the mood of the on-duty SRE engineers.
In December, we will hold another .
We'll have a small retrospective. Remember how just a few years ago HRs were racing to see who could recruit more DevOps engineers for their companies? The prize has changed. Now they, like the surveillance system "Pantsir-S1", are scanning the surroundings for SRE engineers. I mentioned in the article "", what it's like to be an SRE engineer at Google, and how even such a corporation faces a shortage of SRE specialists.
At the online intensive in December, over three days, from 10:00 AM to 7:00 PM, you will learn how to ensure the performance, resilience, and availability of websites under limited resources, eliminate IT incidents, and conduct post-mortems so that problems do not repeat.
Course speakers:
Ivan Kruglov. Staff Software Engineer at Databricks. Has experience in enterprise companies with distributed messaging delivery and processing, Big Data and web stack, internal cloud building, and service mesh.
Pavel Selivanov. Senior DevOps Engineer at Mail.ru Cloud Solutions. Has built dozens of infrastructures and written hundreds of CI/CD pipelines. Certified Kubernetes administrator. Author of several courses on Kubernetes and DevOps. Regular speaker at Russian and international IT conferences.
Everything will be intense, unpredictable, and hands-on. You will build, break, and fix things — sometimes in very different sequences.
Build: You will need to formulate SLO, SLI, and SLA metrics for a website made up of several microservices; develop the architecture and infrastructure to support them; assemble, test, and deploy the site; set up monitoring and alerting.
Break: You will examine internal and external factors that degrade SLO: developer errors, infrastructure failures, traffic spikes, DoS attacks. Learn to assess resilience, error budget, testing practices, interruption management, and operational load.
Fix: You will be trained to quickly and efficiently organize a team for incident resolution within the shortest timeframe: engage colleagues, notify stakeholders, and establish priorities.
Study: You will analyze the approach to the website from an SRE perspective. Review incidents. Determine how to avoid them in the future: improve monitoring, change architecture, development and operational approaches, and regulations. Automate processes.
simulates real conditions — the time to restore service functionality will be extremely limited. Just like in real life, in a true working situation.
You can find the terms of the SRE course and study the full program at .
The online intensive is scheduled for December 2020. For those who pay in advance, we have prepared a discount.
Ready for intense learning, unconventional tasks, and unexpected emergencies?
It won't be easy — that's for sure. There will be professional growth.
Source: habr.com
