Site Reliability Engineering (SRE) is an approach to running production systems that applies software engineering to operations. It sets measurable reliability targets and replaces repetitive manual work with automation.
DevOps is a broad way of working that joins development and operations; SRE is one concrete way to run production, using SLOs and error budgets. Many teams use both, with SRE practices sitting inside a wider DevOps culture.
An incident postmortem is a written review held after an outage or serious failure. It records what happened, why it happened and how the response went, then commits to specific changes that make a repeat less likely.
Kanban is a method for managing work by showing it on a board and limiting how much is in progress at once. Tasks flow continuously from start to finish rather than in fixed sprints.
Managed services is an engagement where an outside provider runs a system or function, such as cloud infrastructure or support, against agreed service levels. The client buys an ongoing outcome rather than paying for individual people or hours.
Observability is the ability to understand what a running system is doing, and why, from the data it emits. That data is mainly logs, metrics and traces, which let engineers answer new questions without shipping new code.
A service level objective (SLO) is an internal reliability target for a service, such as the share of requests that must succeed quickly. It defines what good enough looks like for users over a rolling window.
A clear proven process, that delivers
You've seen our ideas - now go deeper.
Discover more insights, guides, and engineering practice.