Solution ideas
This article is a solution idea. If you'd like us to expand the content with more information, such as potential use cases, alternative services, implementation considerations, or pricing guidance, let us know by providing GitHub feedback.
This solution idea describes how to tier data and applications on-premises and on Azure. As data flows into a storage account, you can use Azure Stack to analyze the data for anomalies or compliance and to display insights in apps.
Architecture
Download a Visio file of this architecture.
Dataflow
- Data flows into a storage account.
- Function on Azure Stack analyzes 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.
Components
- Storage: Durable, highly available, and massively scalable cloud storage
- Azure Functions: Process events with serverless code
- Azure Stack: Build and run innovative hybrid applications across cloud boundaries
Scenario details
This scenario can help you tier data and applications on-premises and on Azure. Filter unnecessary data early in the process, bring cloud applications close to the data on-premises, and analyze large-scale aggregate data from multiple locations on Azure.
Potential use cases
Tiered applications provide the following benefits:
- The ability to update the technology stack of one tier without affecting other areas of the application.
- Development teams work on their own areas of expertise.
- Able to scale the application.
- Adds reliability and more independence of the underlying servers or services.