About This Architecture

AgilePay's production infrastructure on Azure spans three tiers across a VNet with public, private application, and data subnets, secured by Front Door, WAF, and Application Gateway. Traffic flows from users through CDN and Front Door to Application Gateway in the public subnet, then to API and identity servers in the private application subnet, with databases isolated in the data subnet. The architecture separates legacy monolithic services (Web Ops Portal, Web Client Portal, PDW, Base App) from modern microservices (AgileAPI, ClientAPI, SupportAPI, IDS Identity Server) while maintaining replication and failover capabilities. A dedicated resource group handles PR Batch orchestration via Service Bus queues and topics, enabling asynchronous payroll and reporting jobs with status monitoring. Fork this diagram to customize subnetting, add availability zones, or integrate additional Azure services like API Management or Azure Functions.

People also ask

How do you design a multi-tier Azure VNet architecture for a payroll platform with legacy and modern APIs?

AgilePay's architecture isolates public, application, and data subnets within a VNet, uses Front Door and WAF for edge security, routes traffic through Application Gateway to microservices (AgileAPI, ClientAPI, IDS), maintains legacy services separately, and orchestrates asynchronous payroll jobs via Service Bus queues and topics with monitoring via Application Insights.