Availability within an AWS Region
appTRAKER runs on Amazon Web Services using multiple layers of redundancy, replication, monitoring and recovery. The design addresses routine infrastructure failures within a Region as well as broader events that require disaster recovery.
Application resources can operate across multiple Availability Zones, which are separate infrastructure locations within an AWS Region. Elastic Load Balancing distributes traffic across healthy capacity in multiple Availability Zones.
Database resilience
Amazon RDS Multi-AZ maintains synchronized database redundancy in another Availability Zone and can fail over when the primary database experiences an infrastructure problem. Backups provide an independent recovery layer.
Cross-Region disaster recovery
For customer environments configured for cross-Region recovery, LAUNCHER can maintain database replicas, replicated application resources and recovery infrastructure in a second AWS Region. Amazon S3 cross-Region replication can also protect applicable documents and objects associated with loan applications.
Multi-AZ provides high availability inside a Region. Cross-Region replication provides an additional recovery path for a regional event.
Independent backup and recovery layer
Replication and backups serve separate resilience and recovery purposes. LAUNCHER maintains encrypted backups and documented restoration procedures for events where a replicated system is unavailable, inappropriate to use or affected by a data-integrity problem.
Traffic protection and monitoring
AWS Web Application Firewall helps filter malicious and abusive requests before they reach internet-facing application resources — part of the wider security program.
Monitoring and alerts cover critical application infrastructure, databases, replication, storage and backup processes. Automated actions handle suitable failure conditions; the operations team investigates those that require judgment.
Business continuity and recovery
LAUNCHER maintains documented Business Continuity and Disaster Recovery procedures for system recovery, restoration, regional failures, customer communication and personnel responsibilities. Recovery procedures are periodically exercised and validated against system criticality, business requirements and applicable customer agreements.
A layered approach
What varies by environment
Recovery objectives, cross-Region capabilities and customer responsibilities vary by implementation and agreement. The applicable design is confirmed during due diligence.
Lending infrastructure built for resilience
Layered application, database, replication, backup, traffic-protection, monitoring and recovery controls support continued lending operations.
appTRAKER combines AWS cloud capabilities with LAUNCHER-operated monitoring, replication, backup, recovery and continuity processes to build resilience throughout the lending environment.
Redundant infrastructure. Replicated data. Documented recovery. One resilient lending platform.
Frequently asked questions about availability
How does appTRAKER respond to an Availability Zone disruption?
Traffic can continue through healthy application resources in other configured zones, while RDS Multi-AZ can fail over database operations to its synchronized standby.
What happens if an entire AWS Region is affected?
Applicable environments can use cross-Region database, object and infrastructure resources as part of the documented recovery process.
Are appTRAKER databases replicated?
Amazon RDS Multi-AZ maintains a synchronized standby within the Region, and environments configured for cross-Region recovery can also maintain replicas in a second AWS Region.
Are loan documents replicated?
Customer environments configured for cross-Region disaster recovery can use Amazon S3 replication to maintain copies of applicable documents and objects in another AWS Region.
Does appTRAKER maintain backups?
Yes. LAUNCHER maintains encrypted backups and documented restoration procedures, kept independent of replication so a data-integrity problem does not propagate to every copy.
How does LAUNCHER test disaster recovery?
LAUNCHER maintains documented Business Continuity and Disaster Recovery procedures incorporating monitoring, recovery validation, backup review, replication testing and disaster-recovery exercises.
How does LAUNCHER plan for service interruption and recovery?
LAUNCHER uses redundant infrastructure, replication, failover, backups, monitoring and documented disaster-recovery procedures designed to reduce the likelihood and impact of service interruptions.