All case studies / Olo
){kind=logo}
Olo deploys hundreds of microservices twice daily with Octopus
About Olo
Olo is one of the largest and most flexible restaurant commerce ecosystems in the United States.
Olo's software enables restaurants, convenience stores, and supermarkets to scale online ordering and delivery, make data-driven business decisions, and personalize the guest experience on- and off-premise. As a leading open SaaS platform, Olo enables over 600 brands to jointly reach 85 million connected guests across approximately 82,000 locations, processing more than 2 million orders per day on average.
Challenges
Olo needed to manage complex daily deployments while scaling
Olo's deployments are complex because its software integrates with over 300 technology solutions and they are tailored to the unique needs of each brand. Olo's customers update their menus in real time and use various payment processing platforms. To support this complexity, Olo needed a tool that could deploy consistently and allow the company to scale as it grew.
Olo has around 40 DevOps engineers split into teams, and each team continually deploys iterations of the product. To meet customer demand, the teams must deploy multiple times daily. Olo needed an automated deployment solution that removed the burden of release management and let the engineers focus on continuous improvement. Deployments need to work consistently and quickly in their fast-evolving environment.
We integrate with so many different technologies that we need to constantly iterate and improve on the product. Octopus gives us the ability to deploy quickly and consistently despite the complexity of our deployments.
Solution
Continuous iteration and Config as Code lets Olo deploy twice daily
Olo chose Octopus Deploy to manage its complex deployments and releases. Olo’s business-critical project has 116 steps and 30 child projects with around 20 additional steps. To avoid support issues, Olo needs to deploy this project up to twice per day. Octopus Deploy lets the team continually iterate on and enhance the product, automating their complex deployment process and giving the developers time back to focus on improvements.
As the company scales, Olo continues to take advantage of new Octopus features to make deployments more effective. They use Configuration as Code in Octopus to accelerate their software delivery, while ensuring compliance with The Sarbanes-Oxley Act (SOX), which requires separation of duties.
Using Config as Code has made things so much simpler and faster. It's allowed people who normally wouldn't contribute to a deployment process to do so.
Olo's CI / CD pipeline
)
)
Value
How Octopus simplifies deployments and saves time for Olo
Complex deployments simplified
Using Octopus Deploy continues to improve Olo’s deployments. The DevOps teams use the Tenants feature to consistently test and release many deployments per day across approximately 600 on-demand environments.
Shorter release cycle
For Olo’s business critical project, Octopus Deploy helps Olo’s team to:
- Deploy twice daily
- Reduce deployment time to 17 minutes
- Substantially reduce the number of support tickets they receive
- Regularly achieve one-ticket deployments (without any deployments for 2 days, the team expects upward of 60 support tickets)
Continuous improvement and quicker time to value
Automating deployments means Olo’s teams can focus on product innovation and continuing to deliver value to its clients. Olo is confident deployments will proceed consistently across its complex environments, allowing the software engineers to stay focused on developing the product instead of worrying about moving it to production.
Time savings
By using Config as Code for Octopus, Olo's developers can easily repeat deployment processes across multiple projects, simply by copying the code to new projects and changing the variables.
I have teams here that deploy API docs once an hour, and that’s pretty impressive. The great thing is that it happens as “no event” - they just build the release and send it to Octopus. Nobody has to worry about what’s going on with deployments, and they don’t need to. It just works.