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.
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.
A canary release ships a new version to a small share of users or servers first. The rollout widens only if error rates, latency and other health metrics stay within agreed limits.
Disaster recovery is the set of plans, tools and procedures for restoring systems and data after a major outage, data loss or regional failure. It aims to resume service within agreed time and data-loss limits.
A load balancer is a network component that spreads incoming requests across several servers or containers. It keeps any single instance from being overloaded and steers traffic away from unhealthy ones.
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 agreement (SLA) is a provider's contractual commitment to meet measurable standards such as availability or response time. It also sets the remedies that apply when those standards are missed.
A clear proven process, that delivers
You've seen our ideas - now go deeper.
Discover more insights, guides, and engineering practice.