This provides a prescriptive solution platform design coupled with Azure best practices and design principles. These principles serve as a compass for subsequent design decisions across critical technical domains. The architecture will continue to evolve alongside the Azure platform and is ultimately driven by the various design decisions that organizations must make to define their legacy workload journey.
The architecture consists of two core building blocks:
- Azure Core Landing Zone hub - provides all centralized network traffic management capabilities for the solution platform and on-premises connectivity of an organization.
- Solution Specific Landing Zone - is a logical construct and a unit in the solution architecture that enables execution of Mainframe, Midrange modernization components.
This Landing Zone architecture represents the strategic design path and target technical state for your Mainframe, Midrange workloads on the Azure platform.
Note: Before getting started with the deployment, please make sure you are familiar with the complementary documentation in the Cloud Adoption Framework.
The enterprise architecture is broken down into six different design areas, where you can find the links to each at:
- Input comes from remote clients via ExpressRoute, or from other Azure users. TCP/IP is the primary way to connect to the system. On-premises users can access web-based applications over Transport Layer Security (TLS) port 443.
- Azure Load Balancer manages access to the application compute clusters. Load Balancer supports scale-out compute resources to handle input.
- Application compute clusters run on Azure VMs. Compute resources use solid-state drive (SSD) managed disks with Accelerated Networking.
- Application servers in the compute clusters host the applications based on language capability, such as Java classes or COBOL programs. The servers receive application input, and share application state and data by using Azure SQL database.
- Data services in the application clusters support multiple connections to persistent data sources. Azure Private Link provides private connectivity from within the virtual network to Azure services.
- Data storage consists of high-performance storage with premium SSD disks, Azure Files, and standard storage, including blob, archive, and backup storage.
- Azure PaaS data services provide scalable and highly available data storage that you can share among compute cluster resources.
- Services can easily integrate with the modernized system.
Please ensure you have verified and completed all prerequisites described here
To deploy the Landing Zone into your Azure Subscription, please follow the step-by-step instructions:
- Select and deploy one of reference implementations below:
| Reference implementation | Deploy to Azure |
|---|---|
| Generic Containerized Solution |  |
| Raincode Metal Linux Solution | |
| Stromasys Solution | |
| Opentext Solution | |
| TmaxSoft Solution | |
| Luminex Solution | |
| Tidal Solution | |
Please leverage issues if you have any feedback or would like to submit a request to improve the solution hosted in this repository.
The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services.
Telemetry collection is on by default.
Please review the Contributor's Guide for more information on how to contribute to this project via Issue Reports and Pull Requests.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.