Reliability, Platform & Developer Experience

Site Reliability Engineering

Applying software engineering to operations so services meet explicit reliability goals.

Building internal platforms for delivery teams

A discipline that creates reusable self-service capabilities and reduces the cognitive load of shipping software.

Internal Developer Platform

A curated internal layer of tools, services and workflows that lets teams build and operate software consistently.

Developer Experience

How easily and effectively developers can understand, build, test, ship and operate software in an organisation.

A supported route for a common engineering task

A documented, automated and optional path that makes the preferred way to build or deploy the easiest way.

Users obtain a capability without a manual hand-off

Platform access that lets teams provision or operate standard resources through safe automated interfaces.

Repetitive manual operational work

Work that is automatable, tactical and scales with service growth without creating lasting value.

The person coordinating an incident response

A temporary role responsible for direction, priorities and communication during a significant incident.

Rules for involving additional responders

A defined sequence for paging people or teams when an alert is not acknowledged or needs greater authority.

Learning from failure without scapegoating

An operating principle that examines system conditions and decisions so incidents produce learning rather than fear.

Reduced attention caused by too many alerts

The risk that noisy or low-value notifications make responders slower to notice important signals.

A system that notifies the on-call responder

The alerting mechanism or service used to wake or contact the person responsible for urgent response.

A guide for handling a known operational scenario

Step-by-step or decision-based guidance for responding consistently to a recurring situation.

A discoverable inventory of internal services

A maintained index of systems, owners, interfaces, dependencies and operational information.

A check that a service can perform its role

An endpoint or probe used to decide whether an instance is alive, ready or functioning correctly.

Scripted checks that simulate user activity

Monitoring that runs controlled transactions from test locations to detect availability and performance problems.

Real User Monitoring

Measuring performance and errors from actual user sessions in browsers or apps.

Following one request across services

Telemetry that links spans from multiple components to reveal a request's path and timing.

Recording discrete events from a system

Creating timestamped records that help explain behaviour, errors and security-relevant activity.

Numeric measurements collected over time

Aggregated values such as request rate, error rate or latency used to understand system behaviour.

Data emitted to understand a system

The logs, metrics, traces and related signals collected from running software and infrastructure.

Forecasting resources needed for demand

Estimating future traffic and resource requirements so a service can meet its objectives economically.

Testing resilience through controlled failure

A practice of introducing planned faults to learn how systems behave and improve their ability to recover.

A rehearsed operational scenario

A planned exercise in which teams practise responding to failure, disaster or security situations.