Delivering Continuous Innovation: Thousands of Releases a Year with Zero Downtime¶
Date: ~2023 (second edition) Author: Thor Henning Hetland
The second edition of this talk. More polished framing, same core thesis — a small team delivering thousands of releases per year with zero downtime. The agenda: Premises and Achievements, Context and Scope, Unique Approaches, Key Differences.
What the talk covers¶
Culture. Three pillars: problem-solving focus (finding solutions, no excuses), learning-centric (optimising for continuous improvement at speed), and hypothesis-driven development (code to test hypotheses, validate with customers, limit waste as the software grows).
Embracing failure. A four-level pyramid: Plan to Fail → Fail Fast → Learn from Failure → Adapt and Improve. The belief that lessons from failure are the best kind of learning, enabling faster iteration and better long-term results.
Core services. Bespoke Software Development, Cloud-Native Solutions, Maintenance and Operations — framed as a single full-lifecycle offering, not separate engagements.
Expertise. 24/7 Always-On Systems (no downtime, no service windows), Rapid Scaling (10× traffic increases in hours or days), Fast Market Adaptation (continuous releases multiple times per day), Cybersecurity Focus.
The unique approach. Four pillars: 24×7 distributed organisation across most time zones, cloud-native and microservice by default, employing top talent to push technological limits, and investing in custom libraries and tooling to boost efficiency.
Partnership model. Customers decide WHAT needs to be done. eXOReaction decides HOW. The team identifies itself as the customer's own IT development and operations department — tight integration, not arm's-length consulting.
Rethinking best practices. Critically examining industry conventions rather than following them blindly, continuously evaluating and replacing methods that do not deliver better results.
Key performance indicators:
| Metric | Value |
|---|---|
| MTTR | 5–20 minutes (>90% of issues, often before customer notification) |
| MTBF | 5+ years |
| Lines of Code per Developer per Year | 20,000–100,000 |