DORA
DORA is a research and measurement framework for software delivery performance, commonly using deployment frequency, lead time for changes, change failure rate, and time to restore service.
Platform Engineering on Kubernetes
A DORA metric is a software delivery performance measure from the DORA research program, including delivery speed, throughput, and stability dimensions.
- How it is used
- Uses delivery and recovery measurements to assess whether platform changes improve software-delivery performance.
- How deep it goes
- Defines four delivery metrics and outlines collection and calculation stages; defers the fifth, reliability-focused metric.
- Examples
- Uses a deployment-frequency pipeline that stores CloudEvents, transforms them into CDEvents, and calculates metrics from PostgreSQL.
- What you can do after
- Evaluate/understand platform delivery performance and identify bottlenecks using metrics aggregated from delivery systems.
Effective Platform Engineering
The DORA framework is a software delivery performance framework centered on deployment frequency, lead time for changes, change failure rate, and time to restore service.
- How it is used
- Uses four delivery and reliability outcomes to evaluate platform effectiveness and connect engineering performance with business value.
- How deep it goes
- Defines all four measures and supplements them with leading indicators, while stopping short of prescribing a complete measurement implementation.
- Examples
- Uses Epetech’s deployment, pipeline-stage, automation, code-quality, and testing indicators as practical measurement examples.
- What you can do after
- Evaluate delivery performance and diagnose bottlenecks by combining DORA outcomes with leading engineering indicators.
"Looks Good to Me"
A software delivery performance measure covering deployment frequency, change lead time, time to restore service, or change failure rate.
- How it is used
- Uses four delivery measures to evaluate engineering performance, support code-review conversations, and identify process improvement opportunities.
- How deep it goes
- Defines four metrics, explains their organizational relevance, and classifies teams into four performance categories.
- Examples
- Uses metric tables comparing deployment frequency, change lead time, restoration time, and failure rate across performance levels.
- What you can do after
- Evaluate team performance by collecting and analyzing four delivery metrics, then use the results to guide improvement.
Architecture Modernization: Socio-technical alignment of software, strategy, and structure
DORA metrics are software delivery performance measures covering deployment frequency, lead time for changes, change failure rate, and time to restore service.
- How it is used
- Uses delivery performance measures to assess modernization progress, deployment capability, and operational reliability.
- How deep it goes
- Defines four delivery measures and positions them as indicators for assessing change speed and system reliability.
- Examples
- Uses deployment frequency, lead time for changes, change failure rate, and time to restore service as its measures.
- What you can do after
- Evaluate modernization progress through delivery speed, deployment frequency, change reliability, and service recovery.
Grokking Software Architecture
DORA metrics measure software delivery performance through deployment frequency, change lead time, change failure rate, and recovery time.
- How it is used
- Uses four delivery measures as architectural feedback on the balance between deployment speed and production stability.
- How deep it goes
- Defines all four measures and connects their results to architectural coupling, testability, and recovery.
- Examples
- Contrasts quarterly monolith releases with multiple daily service deployments and weeks-long versus minutes-long change lead times.
- What you can do after
- Evaluate architectural boundaries by interpreting delivery speed and stability signals together.
Also covered in
- Microservices Patterns, Second EditionIn early access (MEAP)
- Google Anthos in Action
- Think Like a Software Engineering Manager
What to know first
- deployment pipelineA deployment pipeline is a repeatable sequence of stages that builds, tests or validates, packages, and delivers software changes toward release or deployment.
- DevOpsDevOps is an organizational and technical approach that integrates software development and IT operations through collaboration and automation to improve software delivery and operation.
- monolithic architectureMonolithic architecture is a software architectural style in which an application's major functionality is organized and deployed as a single unit.
Related concepts
- change failure ratehas part · Change failure rate is the proportion of deployed software changes that cause failures requiring remediation, rollback, recovery, or other corrective action.
- deployment frequencyhas part · Deployment frequency is the rate at which software changes are deployed to a target environment, such as production.
- lead timehas part · Lead time is the elapsed time from when work is initiated or becomes available until its result is completed, delivered, or made available to its recipient.
- mean time to resolutionhas part · Mean time to resolution is the average elapsed time from identifying or reporting an issue, failure, or incident until it is resolved or affected service is restored.
Questions about DORA
What is DORA?
DORA is a research and measurement framework for software delivery performance, commonly using deployment frequency, lead time for changes, change failure rate, and time to restore service.
Which Manning books explain DORA?
Platform Engineering on Kubernetes, Effective Platform Engineering, "Looks Good to Me", Architecture Modernization: Socio-technical alignment of software, strategy, and structure and Grokking Software Architecture.
What should I know before learning DORA?
Manning books that teach DORA usually introduce deployment pipeline, DevOps and monolithic architecture first.
What are the parts of DORA?
DORA includes change failure rate, deployment frequency, lead time, mean time to resolution and change lead time.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.




