Today we are happy to announce the rollout of our new multi-region architecture, designed to elevate the reliability of our platform while reinforcing its capabilities for disaster recovery (DR), ensuring a robust experience for our users.
The new architecture is shaped around an active/passive recovery strategy, leveraging a blend of AWS services within a multi-region framework.Â
Data synchronization is maintained across two distinct AWS regions, facilitated by a continuous deployment pipeline and perpetual code updates for the compute layer in both regions. This ensures that a ready backup is always kept in reserve, in a second region, to be rapidly utilized in the event of a failure.
New 30 Minutes RTOÂ
An efficient disaster recovery plan depends on two central metrics. Those are:
- Recovery Time Objective (RTO) - the the maximum amount of delay that’s acceptable between disrupting and restoring of service)
- Recovery Point Objective (RPO) - the maximum amount of time without a set ‘data recovery point’Â
In essence, RTO and RPO are metrics that directly impact the organization's ability to weather unforeseen events. They provide a framework for establishing realistic recovery goals, enabling businesses to plan and implement effective strategies for minimizing disruptions, safeguarding data, and maintaining operational continuity.Â
This, in turn, contributes to overall business resilience and the ability to navigate challenges with minimal impact.
And of course, these are figures measured in minutes - not days.
With a focus on minimizing downtime, our new architecture boasts a RTO of just 30 minutes. In the unlikely event of such a failure, our system transitions to the passive environment to swiftly restore full functionality.
Additionally, our RPO stands at an impressive 180 minutes (three hours), ensuring minimal data loss in the rare occurrence of a setback.
Our backups protect data from RDS, DynamoDB, S3 buckets, EFS, Key Management Service (KMS), and the AWS Secrets Manager.
This backup assures high availability by initiating failover (shifting traffic to the 2nd region) and failback (returning traffic to the first region).
Assembling AWS Toolbox
At env0, our AWS experience is extensive, so we wanted to ensure a robust yet stable multi-region setup for all our services. After concerted research and testing, we landed on supporting a mix of AWS tools to replicate critical elements of our platform:
- DynamoDB Global Tables – Ensuring seamless data replication across regions for consistent performance.
- RDS Global Cluster – Facilitating effortless database replication to enhance data redundancy and disaster recovery capabilities.
- Secrets Manager Replication – Strengthening our security framework by duplicating and synchronizing secrets across regions.
- KMS Replication – Extending key management capabilities across regions for secure and compliant cryptographic key handling.
- EFS Replication – Enabling reliable and scalable replication of file systems across regions.
Extensive examination and successful integration of these solutions have allowed us to present our customers with a comprehensive multi-region solution, reflecting env0's commitment to delivering excellence in security, performance and reliability.
Reliable Infrastructure = Strong Business Foundation
Working with some of the world’s largest enterprises, including names like VMware, PayPal, and Western Union, we have to be constantly mindful of the high availability, reliability and security.Â
The upgrade of our new multi-region infrastructure and the 30-minute Recovery Time Objective equips our customers with the solid foundation they need to grow their business - contribute to their ability to optimize business processes, uphold regulatory standards, predictably meet Service Level Agreements (SLAs), and more.
This empowers our customers to focus on their businesses, confidently knowing that even in the most extreme scenarios, our platform is poised to ensure their business continuity.
To learn more, book a technical demo to see our platform in action.Â
Today we are happy to announce the rollout of our new multi-region architecture, designed to elevate the reliability of our platform while reinforcing its capabilities for disaster recovery (DR), ensuring a robust experience for our users.
The new architecture is shaped around an active/passive recovery strategy, leveraging a blend of AWS services within a multi-region framework.Â
Data synchronization is maintained across two distinct AWS regions, facilitated by a continuous deployment pipeline and perpetual code updates for the compute layer in both regions. This ensures that a ready backup is always kept in reserve, in a second region, to be rapidly utilized in the event of a failure.
New 30 Minutes RTOÂ
An efficient disaster recovery plan depends on two central metrics. Those are:
- Recovery Time Objective (RTO) - the the maximum amount of delay that’s acceptable between disrupting and restoring of service)
- Recovery Point Objective (RPO) - the maximum amount of time without a set ‘data recovery point’Â
In essence, RTO and RPO are metrics that directly impact the organization's ability to weather unforeseen events. They provide a framework for establishing realistic recovery goals, enabling businesses to plan and implement effective strategies for minimizing disruptions, safeguarding data, and maintaining operational continuity.Â
This, in turn, contributes to overall business resilience and the ability to navigate challenges with minimal impact.
And of course, these are figures measured in minutes - not days.
With a focus on minimizing downtime, our new architecture boasts a RTO of just 30 minutes. In the unlikely event of such a failure, our system transitions to the passive environment to swiftly restore full functionality.
Additionally, our RPO stands at an impressive 180 minutes (three hours), ensuring minimal data loss in the rare occurrence of a setback.
Our backups protect data from RDS, DynamoDB, S3 buckets, EFS, Key Management Service (KMS), and the AWS Secrets Manager.
This backup assures high availability by initiating failover (shifting traffic to the 2nd region) and failback (returning traffic to the first region).
Assembling AWS Toolbox
At env0, our AWS experience is extensive, so we wanted to ensure a robust yet stable multi-region setup for all our services. After concerted research and testing, we landed on supporting a mix of AWS tools to replicate critical elements of our platform:
- DynamoDB Global Tables – Ensuring seamless data replication across regions for consistent performance.
- RDS Global Cluster – Facilitating effortless database replication to enhance data redundancy and disaster recovery capabilities.
- Secrets Manager Replication – Strengthening our security framework by duplicating and synchronizing secrets across regions.
- KMS Replication – Extending key management capabilities across regions for secure and compliant cryptographic key handling.
- EFS Replication – Enabling reliable and scalable replication of file systems across regions.
Extensive examination and successful integration of these solutions have allowed us to present our customers with a comprehensive multi-region solution, reflecting env0's commitment to delivering excellence in security, performance and reliability.
Reliable Infrastructure = Strong Business Foundation
Working with some of the world’s largest enterprises, including names like VMware, PayPal, and Western Union, we have to be constantly mindful of the high availability, reliability and security.Â
The upgrade of our new multi-region infrastructure and the 30-minute Recovery Time Objective equips our customers with the solid foundation they need to grow their business - contribute to their ability to optimize business processes, uphold regulatory standards, predictably meet Service Level Agreements (SLAs), and more.
This empowers our customers to focus on their businesses, confidently knowing that even in the most extreme scenarios, our platform is poised to ensure their business continuity.
To learn more, book a technical demo to see our platform in action.Â
.png)
