Microsoft Azure is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.
For a variety of reasons, users may wish to mount a persistent volume on two or more pods spanning multiple availability zones. One such use case is to make data stored outside of IRIS available to both mirror members in case of failover.
Unfortunately the built-in storage classes in most Kubernetes implementations (whether cloud or on-prem) do not provide this capability:
We currently have Business Operation that we built to use the EnsLib.SQL.OutboundAdapter so we can make Microsoft SQL Server Stored Procedure calls. The BO is attached to a Java Gateway Service.
Some of our MS SQL Databases have moved from being OnPrem to Azure Cloud. We have started seeing where we are receiving errors on the BO saying that we cannot connect to the Azure Database, but we never receive a Disconnect from the Azure Database.
In my last article, I went through a walkthrough on how you can try deploying InterSystems IRIS Community Edition, or IRIS for Health Community Edition for free on AWS. In this follow up, I will show the same for the next biggest cloud provider, Microsoft Azure.
Like with AWS, Azure also provides a free offering on sign up, although its a bit less generous - you get $200 free credit to spend in the first month. This does mean you can once again try deploying IRIS Community edition for free on Azure, although I do recommend caution to avoid costly bills.
Year