Azure Stack tiered data for analytics
Easily tier data and applications on-premises and in Azure with architecture that supports greater efficiency in applications. Filter unnecessary data early in the process, easily bring cloud applications close to the data on-premises and analyse large scale aggregate data from multiple locations in Azure for fleet-level insights.
Data flows into a storage account.
Function on Azure Stack analyses the data for anomalies or compliance.
Locally relevant insights are displayed on the Azure Stack app.
Insights and anomalies are placed into a queue.
The bulk of the data is placed into an archive storage account.
Function sends data from queue to Azure Storage.
Globally relevant and compliant insights are available in the global app.
- 1 Data flows into a storage account.
- 2 Function on Azure Stack analyses the data for anomalies or compliance.
- 3 Locally relevant insights are displayed on the Azure Stack app.
- 4 Insights and anomalies are placed into a queue.
- 5 The bulk of the data is placed into an archive storage account.
- 6 Function sends data from queue to Azure Storage.
- 7 Globally relevant and compliant insights are available in the global app.
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.