InfoQ Homepage Site Reliability Engineering Content on InfoQ
-
Scaling Infrastructure as Code at Challenger Bank N26
To launch their banking platform globally in the US, Brazil, and beyond, the challenges bank N26 introduced a new layer for the configuration of regions in their architecture, where product development teams can add application needs. At FlowCon France, Kat Liu presented why and how they introduced this layer, the benefits that it brings, and the things they learned.
-
The Importance of Fun in the Workplace
Things at work that make us smile or laugh can improve team cohesion, productivity and organisational performance. Fun can’t be forced, but it can be fostered, said Holly Cummins at FlowCon France 2019, where she spoke about the importance of fun in the workplace.
-
How Did Things Go Right? Learning More from Incidents at Netflix: Ryan Kitchens at QCon New York
At QCon New York, Ryan Kitchens presented “How Did Things Go Right? Learning More from Incidents”. Key takeaways from the talk included: recovery is better than prevention; an incident occurs when there is a “perfect storm” of events -- there is no root cause; “stop reporting on the nines”, as user happiness is more important; and there is value in learning how things go right.
-
The Evolution of Full Cycle Developers at Netflix: Greg Burrell at QCon SF
At QCon San Francisco, Greg Burrell talked about the journey towards “full cycle developers” within the Netflix edge engineering team. Following the principle of “operate what you build”, developers within this team chose to take on more operational responsibility for their services, and were facilitated by comprehensive tooling, training and management support.
-
GitHub Incident Analysis Shows How to Improve Service Reliability
On October 21, 2018, GitHub users experienced a degraded service during 24 hours due to an incident caused by routine maintenance work. This led to the display of outdated and inconsistent information and to the unavailability of webhooks and other internal services for 24 hours. GitHub post-incident report shows where things failed and suggests how to improve site reliability.
-
Google Explains Why Others Are Doing SRE Wrong
Stephen Thorne, customer reliability engineer at Google, recently spoke at the DevOps Enterprise Summit London on what Site Reliability Engineering (SRE) is and why many organizations are failing to understand its basic premises and benefits.
-
Full Cycle Developers at Netflix: from Mindsets to Self-Service Tooling
The Netflix Tech Blog has shared the story of the “Edge Engineering” team’s journey of experimenting with approaches to building and operating services, which has culminated in “Full Cycle Developers”. This approach is showing promise with Netflix, where developers are responsible for certain operational aspects of service delivery, and are supported through a range of self-service tooling.
-
From Darwin to DevOps: John Willis and Gene Kim Talk about Life after The Phoenix Project
IT Revolution recently published an audiobook with nearly eight hours of conversation between Gene Kim and John Willis; Beyond the Phoenix Project – the Origins and Evolution of DevOps.
-
Microservices and Site Reliability Engineering
A recent article talks about how the complexities introduced by microservices initially seem at odds with the concept of Site Reliability Engineering (SRE), and how companies such as Google are tackling that to ensure that whilst development groups can continue to embrace microservices, they and their SRE teams have the necessary tools and understandings to make them work well together.
-
What It Means to Be a Site Reliability Engineer According to a Survey from Catchpoint
Site Reliability Engineering intersects software engineering with IT Operations and is an approach created at Google in 2003 and described in detail in their 2016 book, Site Reliability Engineering, How Google Runs Production Systems. Digital experience intelligence provider, Catchpoint, surveyed 416 Site Reliability Engineers (SREs) with the goal of understanding what it means to be a SRE.
-
How DevOps Principles Are Being Applied to Networking
Practices from the DevOps world are being adopted into managing networking services. Vendor hardware, configuration tools and deployment modes have eased programmable configuration and automation of network devices and functions.
-
How ING Bank Does SRE
Janna Brummel and Robin van Zijll, from ING Netherlands, talked at the Velocity conference in London about how poor availability from their internet banking systems prompted the bank to implement an SRE culture. A centralized SRE team was set up in the Netherlands to provide tooling, consulting and education on reliability to product teams (known as BizDevOps squads internally).
-
Q&A with Sanjeev Sharma on His DevOpsDays NZ Keynote
Raf Gemmail speaks with IBM's Sanjeev Sharma about his upcoming DevOpsDays NZ closing keynote on the DevOps and SRE lessons we can learn from Apollo 13.
-
Choose Your Own Adventure: Chaos Engineering at QCon New York 2017
Nora Jones, senior chaos engineer at Netflix, talked about chaos engineering at QCon New York 2017. She presents different stages of chaos engineering adoption and gives stories from her previous experiences at Jet and Netflix.