The front end of the application layer uses Azure services like Azure App Service to implement application screens and to interact with users. The Azure Content Delivery Network service caches static content in edge servers for quick response, secured using the Web Application Firewall (WAF) service. These load balancers can coordinate with Azure Application Gateway or Azure Load Balancer for load balancing of the application layer. It routes the requests according to rules defined for the supported workloads. The load balancer can serve a geographically spread user base. Input requests go to a global load balancer service, like Azure Front Door or Azure Traffic Manager. Azure Active Directory (Azure AD) provides authentication. In the migrated system, they interact with Azure applications via public internet or via a private connection implemented with Azure ExpressRoute. Mainframe users are familiar with 3270 terminals and on-premises connectivity. Their usage varies greatly over time, so they benefit from flexible scaling and usage-based pricing.This architecture is ideal for OLTP workloads that have these characteristics: In Architecture, we see how to migrate this architecture to Azure. These services interact with all other services in the system. Concurrently with transaction processing, other services provide authentication, security, management, monitoring, and reporting.Application code uses storage capabilities of the data layer, typically DB2, IMS DB, or VSAM.The transaction managers use the business logic written in COBOL or PL/1 to implement the transactions.In the front end of the application layer, users interact with the CICS/IMS screens or with web pages. ![]()
0 Comments
Leave a Reply. |