Pro V4 HA Architecture Overview
Webscale Pro V4 HA is a next-generation e-commerce hosting environment built on a Decoupled Plane Architecture. By utilizing a “Three-Plane” model, we separate administrative overhead and security processing from your core storefront, ensuring that your customer experience remains fast and resilient across multiple Availability Zones.
1. The Design Philosophy
Decoupling for Performance
In traditional hosting, the “Control” of the server (backups, logging, analytics) happens on the same resources as the “Traffic.” If your logs grow too fast or a backup kicks off during a sale, your site slows down.
- The Pro V4 HA Advantage: We move the “Brain” of the site to a dedicated Control Plane. This ensures that even under heavy management tasks, your Data Plane (the storefront) has 100% of its resources dedicated to serving customers.
Daemonless Container Security
V4 utilizes Podman for container orchestration. This means specific services from Magento to runs as an isolated, rootless process. If one container needs a restart, it doesn’t affect the others, providing a higher level of security and “Self-Healing” stability.
2. Traffic Flow & The AWS Foundation
This section Explains how we utilize AWS services to deliver your site.
- The Edge (AWS Route 53 & CloudFront): Traffic is first routed via AWS Route 53 to the Webscale CDN (CloudFront). This ensures that static assets are served from the global location closest to your customer.
- The Perimeter (Webscale Data Plane): Before reaching your server, requests are scrubbed by the Webscale. This prevents malicious traffic from ever impacting the performance of your site.
- The Core (AWS Services): Your application resides within a secure AWS VPC that spans two Availability Zones. The application is hosted on a pre-defined managed cluster of autoscaling AWS EC2 instances that use Podman containers in each Availability Zone. The storefront and its persistent services (Rabbit MQ, Cron, NFS, and Valkey) are hosted on high-performance AWS EC2 instance, orchestrated by Podman to ensure maximum efficiency. Opensearch resides on the AWS Opensearch AWS service. MYSQL resides on AWS RDS Aurora service. All persistence layer services are replicated across both Availability Zones for high availability.
3. The Pro V4 HA Baseline
This Reference table serves as the technical source of truth for the V4 HA stack.
| Component | Technology | AWS Service utilized | Deployment Location |
|---|---|---|---|
| DNS | Webscale Managed | AWS Route 53 | Global Edge |
| Edge Delivery | Webscale CDN | AWS CloudFront | Global Edge |
| Security | WAF & DDoS Protection | Webscale Data Plane | Perimeter Filter |
| Compute | Proxy & App Layer | AWS EC2 | Shared & Dedicated (Multi-AZ) |
| Orchestration | Podman | Linux Runtime - PHP_FPM Caching (Edge) - Vinyl (Varnish Caching (Data)) - Redis (Tri-Partitioned) | Daemonless Container |
| Search | Opensearch | AWS Opensearch | Shared & Dedicated (Multi-AZ) |
| Cache | Redis/Valkey | AWS Elasticache | Shared & Dedicated (Multi-AZ) |
| Database | MYSQL | AWS RDS Aurora | Shared & Dedicated (Multi-AZ) |
| Storage | Persistent Media | AWS EBS / EFS | Persistent Volume (Multi-AZ) |
| Backups | 7 day snapshot | ||
| SSH | SSH Connect / SSH Gateway |
Feedback
Was this page helpful?
Glad to hear it! Have any more feedback? Please share it here.
Sorry to hear that. Have any more feedback? Please share it here.