We all know that the cloud has revolutionized how apps are developed. But for all the hype and excitement, there are still applications where using the cloud just isn’t an option. Sometimes these applications get forgotten in the rush to the cloud, which can leave some orgs and apps stranded.
So, what do you do when you’ve got an app or legacy system that just can’t be cloud connected?
There are a lot of reasons why this might be the case. Companies in regulated industries may have data that must be kept on premises. Core business systems may not support a cloud model, and replacement may not be an option. Many apps must operate in locations that have limited or no internet connectivity (like the proverbial submarine).
Microsoft Azure Stack
Microsoft’s answer to this challenge can be found in Microsoft Azure Stack.
Azure Stack puts Microsoft Azure services on a hardware appliance that companies can deploy in their own data center. Azure Stack gives you your own on-premises Azure Cloud. Why would you do this? One reason is that it means you can use the same tools to develop and deploy software on-premises and in the cloud. Another is that it makes interoperability between your on-premises and cloud systems much easier. Microsoft has published an excellent white paper to help explain all of this.
3 Main Use Cases for Azure Stack:
Edge and Disconnected
This is where the proverbial submarine comes in. Azure Stack is ideal in situations where there’s no internet connectivity, or the internet connectivity you have is slow, unreliable, or prohibitively expensive, like airplanes, submarines, oil rigs, and ships.
Some organizations, including most financial institutions, have data they can’t share in the public cloud for regulatory or corporate compliance reasons. Azure Stack can enable these organizations to take advantage of Azure while keeping sensitive workloads and data on-premises and isolated.
Cloud on Premises
The cloud has rapidly become a de facto standard for DevOps. Azure stack enables organizations to use the same cloud methodologies when they develop applications in the cloud or on-premises. This is also great for legacy systems that aren’t slated for cloud migration but need to be integrated with cloud systems.