Application Resilience at Deployed
Deployed’s customers have confidence in our platform. It is the core for the most vital work-related tasks in your business, making resilience and availability of utmost importance.
A robust system possesses the capacity to bounce back and sustain functionality even in the face of heavy loads, security threats, or component failures.
The Deployed platform has been crafted with resilience as a primary focus, ensuring you can rely on a durable authoring tool boasting top-tier availability in the market.
Resilient Cloud Infrastructure
Customer data is securely hosted in an Azure production account and Azure SQL, utilizing Azure SQL databases and Azure Blob Storage for object storage.
Deployed takes advantage of Azure's availability zones, which are isolated regions within our selected geographical area to manage infrastructure. This safeguards against failures in one zone affecting others. Azure handles patching, updates, and maintenance seamlessly, ensuring minimal downtime.
Deployed’s source code is hosted within GitHub repositories. These repositories are regularly backed up, and in the unlikely event of catastrophic data loss on GitHub, we can restore our source code from these backups on Azure.
These robust foundations contribute to Deployed's exceptional service availability on the Azure platform.
To ensure the integrity and availability of customer data, Deployed uses Geo-redundant storage. All data is replicated to a paired region. This helps protect against outages that affect backup storage in the primary region.
Recovery Point Objective (RPO) defines the specific point in time to which data should be recoverable. For example, if an organization has an RPO of 1 hour, it means that in the event of a system failure or disaster, they should be able to restore data to a state that is no more than one hour before the incident occurred.
The Recovery Time Objective (RTO) represents the specific moment when system availability can be fully restored, including data up to the predetermined point set by the Recovery Point Objective (RPO).
At Deployed, our Recovery Point Objective (RPO) is set at one hour, and our Recovery Time Objective (RTO) allows for a maximum of 12 hours. In the event of a catastrophic failure, our goal is to recover all data up to one hour before the failure occurred, ensuring full restoration within a maximum timeframe of 12 hours following the failure.