Custom data sovereignty and data gravity requirements
Azure with Azure Stack enables organisations to make technology placement decisions based on business needs – simplifying meeting custom compliance, sovereignty and data gravity requirements.
User enters data into Azure-based web app.
Application commits data to database over virtual network-to virtual network VPN connection to Azure Stack.
Data is stored in SQL database on virtual machine (VM).
- 1 User enters data into Azure-based web app.
- 2 Application commits data to database over virtual network-to virtual network VPN connection to Azure Stack.
- 3 Data is stored in SQL database on virtual machine (VM).
|Provision private networks, optionally connect to on-premises data centres|
|Establish secure, cross-premises connectivity|
Azure SQL Database
|Managed, intelligent SQL in the cloud|
|Process events with serverless code|
|Build and run innovative hybrid applications across cloud boundaries|
Related solution architectures
Implementing a continuous integration/continuous development (CI/CD) approach to deploying applications becomes difficult when on-premises applications are built and operated in different ways to cloud applications. Having a consistent set of development tools and processes across the Azure public cloud and on-premises Azure Stack environments makes it a lot easier for organisations to implement a practice of CI/CD. Apps and services deployed the right way in Azure and Azure Stack are essentially interchangeable and can run in either location.
Azure Stack enables you to deploy Azure services on-premises or in the cloud with a consistent application logic, development paradigm and operations methodology. Hybrid cloud applications are a single system that has components running in both Azure and Azure Stack. This solution blueprint is relevant to establishing connectivity for any application that involves communications between the Azure public cloud and on-premises Azure Stack components. Hybrid connectivity is a foundational blueprint that will be applicable to most Azure Stack solutions. Note: This doesn’t apply to Azure Stack deployments that are disconnected from the public internet.
The need to keep application components on-premises doesn’t have to be a barrier to adopting cloud technologies. With Azure Stack, app components can reside on-premises while interacting with components running in Azure public cloud. This blueprint enables teams to manage identity for users as well as applications in a way that is consistent across clouds.