Case Study Deskcasestudydesk.com
SaaS (Restaurant Commerce)Sourced

Case Study: Olo deploys hundreds of microservices twice daily with Octopus

Olo Case StudySourced & dated by Case Study Desk
Key facts · TL;DR
Company
Olo
Industry
SaaS (Restaurant Commerce)
Challenge
Complex daily deployments at scale
Headline result
17-minute deployments, twice daily, across a 116-step process

Key results

17 min
Deployment time
Business-critical project
2x daily
Deployment frequency
Business-critical project
116
Steps automated in one project
Plus 30 child projects
2M+
Orders processed per day
Across the Olo platform

The challenge

Olo is a large SaaS restaurant commerce platform that enables over 600 brands to reach 85 million connected guests across approximately 82,000 locations, processing more than 2 million orders per day. Its software integrates with over 300 technology solutions, and roughly 40 DevOps engineers must deploy multiple times daily to meet customer demand.

The solution

Olo uses Octopus Deploy with Config as Code and Tenants to automate a business-critical project with 116 steps and 30 child projects, letting teams continually iterate while keeping deployments consistent.

Octopus gives us the ability to deploy quickly and consistently despite the complexity of our deployments.

JD
Jason Dunnivant
Release Engineer, Olo

The results, in context

With Octopus, Olo reduced deployment time for its business-critical project to 17 minutes and deploys it up to twice per day, automating a 116-step process with 30 child projects. The platform processes more than 2 million orders per day on average across the deployments Octopus manages.

Products used

Octopus Deploy Octopus DeployOctopus Deploy Config as CodeOctopus Deploy Tenants