Web Application on Managed Services
Where a replatformed web application lands: one way in at the edge, the app in two zones, its data on managed services.
Requests come in one way: a web application firewall and a content delivery network at the edge, then a managed load balancer; nothing behind it is open to the internet. The application runs on managed Kubernetes in two zones, and its data sits on managed services (PostgreSQL with a standby in the other zone, a cache, a message broker, object and file storage), so patching, backups and failover become the cloud's job.
Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.
When to use it
- A web or API application that keeps its code but hands its plumbing to the cloud: load balancers, brokers, caches, file servers
- Apps already in containers, or ready to run as containers or as autoscaled VMs
- Services that must keep running when one zone fails
Where FleziLift fits
The 7R rule tree sends each web, application and database server here when its facts allow a replatform, naming the target service, readiness and risk on evidence graded L0 to L3. The Wave Plan keeps each application's move group whole, so its load balancer, app servers, database and broker move in one wave through the cutover gates (−28 to +3 days), and the playbook lists each task with the cloud's own tool.
Cloud TransformationThe same pattern, the way each provider builds it
Each cloud's own framework and guidance.
