Solution ideas
This article describes a solution idea. Your cloud architect can use this guidance to help visualize the major components for a typical implementation of this architecture. Use this article as a starting point to design a well-architected solution that aligns with your workload's specific requirements.
This solution idea helps you understand how to improve cross-cloud scalability with solution architecture that includes Azure Stack.
Architecture
Download a Visio file of this architecture.
Dataflow
- A large number of users attempt to access a web app.
- Traffic manager returns the Azure Stack DNS name.
- Users access the Azure Stack web app.
- Once a threshold is reached, a function starts the Azure Web App and enables the Azure Traffic Manager route.
- Traffic is routed to Azure, which can automatically scale App Service.
Components
- Traffic Manager: Route incoming traffic for high performance and availability
- Azure Functions: Process events with serverless code
- Azure Stack: Build and run innovative hybrid applications across cloud boundaries
Scenario details
Modern software is increasingly connected and distributed. The consistency of Azure Stack with Azure infrastructure and platform services enable you to scale resources cross cloud to meet increased load as needed, and decrease resources as demand drops. Optimize cost and maximize resource efficiency while remaining compliant with cross cloud architecture.
Potential use cases
This solution applies to the following scenarios:
- Implement continuous integration and continuous delivery (CI/CD) practices across an Azure Stack Hub implementation and the public cloud.
- Consolidate the CI/CD pipeline across cloud and on-premises environments.
- Develop apps by using both cloud and on-premises services.