Warning alert:We're building our new website - with more examples, tips and docs! Some sections though might still be incomplete or under review. When browsing, keep an eye for progress notes and ways to get updated on particular topics.
Single- or Multi-Region Deployments
Microsoft Azure resources are arranged in Regions and mishmash io follows the same organization - one deployment is typically done in one Region.
Often, to improve the user experience apps are deployed closer to users - say, one instance runs in the USA, another - in EU and a third in Asia Pacific.
To follow the same pattern, mishmash io will be deployed to the same Regions as the app itself. You can choose though if you'd like the app's data to be kept separately on a per-Region basis, or you can have all Regions 'connected' into a single, multi-regional cluster.
In the latter you get an additional benefit - if a Region is completely down others will still handle its share of the data.
Examples
Single region
In this example, an app (My app) is deployed to a single region - eastus. A mishmash io cluster is deployed alongside it, so that the app can benefit from proximity to its database. Further, the app and the custer are deployed in separate Azure Resource Groups so that their resources can be managed separately.
Two regions, without data sharing
Subsequently, a deployment to a second region, westeurope, is performed to reduce the apps's respone times in Europe.
Again, a second mishmash io cluster (mishmash io (2)) is also deployed to the same region, so that the new instance of the app (My app (2)) can also be close to its database.
In this example, the two mishmash io clusters are completely separate - My app (1) in eastus will not be able to work on data stored by My app (2) in westeurope.
Default alert:mishmash io Resource Groups
Note that in this example the two mishmash io clusters are deployed into two separate Resource Groups - Resource group mishmash io (1) and Resource Group mishmash io (2).
Two regions, with data sharing
Warning alert:Important note!
There is no way to 'join' two running mishmash io clusters into a single one.
Doing so would require custom code that 'knows' how to handle potential duplicates in the data.
Take this into consideration when planning your second deployment.
A second region can also be added purely as an extension of an existing mishmash io cluster. This way, data in mishmash io eastus and data in mishmash io westeurope is effectively the data of one single app.
Default alert:mishmash io Resource Groups
Unlike the previous example, here, mishmash io clusters are in the same Resource Group - Resource group mishmash io.
The cluster - mishmash io remains the same, despite running in two regions now.