CLEO Migration Technical FAQs
Why is CLEO being moved to a new infrastructure?
- In short, to further improve reliability. CLEO is now part of the ServiceTitan family, and they are moving the CLEO application so that it runs on the same infrastructure they use to power their other software.
- Currently CLEO is supported by 12 hours per day / 5 days per week monitoring. This leads to outages and slowness being reported by owners first. The migration will come with 24x7 monitoring. The ServiceTitan team will be able to identify any slowness or outages in near real time.
If there is an outage, will ServiceTitan be able to resolve issues faster?
- The ServiceTitan on-call team responds within minutes to an outage. This is backed by an entire Incident Response resolution team.
- This move will come with a vastly larger group of engineers to troubleshoot issues. Any outage will be triaged to the proper channels and ServiceTitan will scramble the team to resolve the issue faster.
- ServiceTitan has dedicated Microsoft resources available to them 24x7 with a very fast response time.
What makes the ServiceTitan infrastructure better than what CLEO is using now?
It is based on more modern tools:
- Kubernetes Clusters are industry standard tools that make web applications highly available and reduce risk to development teams as they build and maintain software.
- CLEO code will run within a Microsoft .NET Core “framework.” .NET Core is a faster and more reliable framework than the existing CLEO framework.
Does ServiceTitan provide infrastructure and data redundancy?
- Infrastructure is highly available and redundant.
- ServiceTitan will continue to use Microsoft Azure SQL databases which have 3 simultaneous copies running in the region, and a secondary region which can be used for failover.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article