We've all heard of and practiced variations of disaster recovery methodologies for achieving 24 X 7 availability for SaaS applications. There is a range of dependencies for optimal RPO (recovery point objective) and RTO ( recovery time objective) including where the application is running, inter-dependencies of microservices, dependencies on datastores, and storage among others. Based on our experience of SaaS-ifying applications to run on hyperscalers, we are identifying patterns for our applications to adopt to optimize RPO (recovery point objective) and RTO ( recovery time objective).

We will describe our challenges, learning, and patterns for next-gen SaaS applications, and guidance on how to adopt them in the delivery of your next SaaS applications running in single or multiple clouds.