Continuity and recovery
What sustains the service when something fails, and what happens to what is already published.
Redundancy
Section titled “Redundancy”The architecture uses redundancy across Availability Zones in AWS to reduce the dependency on a single zone and improve fault tolerance.
The infrastructure is managed through Infrastructure as Code, which allows it to be rebuilt reproducibly instead of depending on manually made configurations.
Backups
Section titled “Backups”Reskyt takes backups of platform data, relying on the mechanisms of the AWS managed services it uses.
The detail of the backup policy is part of the documentation delivered under NDA in an evaluation process. See architecture.
What happens to published apps
Section titled “What happens to published apps”Published binaries remain in the stores and on users’ devices: an interruption of Reskyt services does not remove the installed app or its listing in the stores.
The specific impact of an incident on how the app works depends on the affected component. The architecture uses caching, CDN and decoupling between components to improve the resilience of the service.
Commitments
Section titled “Commitments”The specific continuity commitments applicable to each customer depend on the corresponding contract.
See also reliability and scalability.