Most developers don’t care about multi-cloud. But they should.

Whether developers know it or not, their companies likely already have a multi-cloud environment.   

Multi-cloud is a action where a business selects altered casework from altered cloud providers because some are better for assertive tasks than others. So aggregation X could use cloud A for infrastructure, cloud B for app dev and testing, and cloud C for data localization in a region. 


While commonly advised multi-cloud, this setup really only scratches the apparent of what’s accessible today. That’s because clouds A, B, and C are abandoned from each other from a workflow angle and there’s little or no data administration across them. That’s where the real payoff is for developers.

Data administration has been tough

It’s just been too difficult for developers to build and deploy across clouds. Data administration has been almost impossible, which is why most developers haven’t jumped at the opportunity. 

If they have chosen to do it, it hasn’t been easy. It’s meant:

  • More work
    • To drift or alike any data from one cloud provider to another, developers have had to create and advance bespoke processes. 
  • Living in hope
    • If one cloud region goes down, jumping over to addition is not seamless and after-effects in slower adventures for all.
  • Incompatible operations
    • It’s difficult to secure, monitor, maintain, and govern across clouds.

The barriers amid clouds have always been high. Devs have had to carbon the majority of their appliance code for a second cloud, and even then they still had siloed data sets. 

It’s true that portability for the appliance tier is accepting easier. Kubernetes, chart solutions such as Terraform, and ecology solutions like Datadog have made multi-cloud more manageable. But even in a world where stateless applications can be consistently managed across clouds, having both the data and operations administration keep up has been a beast.

So who’s doing multi-cloud?

Still, business units are agronomics ahead. More than half (55%) of organizations use assorted public clouds, with 21% using three or more, according to a recent IDG report.

Take Panoskin as an example. 

Panoskin’s software allows users to advance custom VR tours of the world and upload them to Google Street View in minutes. The Chicago-based startup currently has 60 actor scenes in its belvedere across 100 countries, with ~18,000 photographers uploading 12,000 new tours monthly. The team uses a multi-cloud action across Google Cloud and AWS to bear better scale and tools to its users.


Another archetype is Ticketek. The aggregation is Australia’s arch ticket benefactor and can handle up to 300,000 ticket sales in less than 30 minutes. It also has data in assorted regions across AWS and Google Cloud, as well as a accessory ticketing belvedere that runs in Google Cloud’s Sydney region. 

Advantages of “true” data sharing

Imagine if you could take modern applications like these one step added and deploy a single data layer across AWS and Google Cloud, or Google Cloud and Azure, or across all of the “big three” at the same time. All after the deployment and interoperability hassles. 

That would give developers the adaptability to choose the best tools and cloud casework for the apps they are building. In other words, use AWS Lambda, Google Cloud’s AI Platform, and Microsoft’s Azure DevOps Casework within a unified console. That’s cool, right? 

It’s now possible. You can accomplish seamlessly across clouds — AWS, Azure, and Google Cloud — with the new multi-cloud clusters adequacy on MongoDB Atlas


Multi-cloud clusters let developers deploy data and apps across all of the altered clouds at the same time, or seamlessly drift from one cloud to the other after downtime. Here’s why you might want to do that: 

  • Pick and mix the best tools across clouds 
    • Developers prefer to work this way, of course. And it gives your aggregation adaptability if, say, a chump prefers a specific cloud provider.
  • Expand apps globally with high availability and low latency
    • No cloud is spared outages. Distribute data across more regions and sleep better at night.
  • Satisfy local data ascendancy requirements
    • Certain geographies are covered by only one cloud provider (for example, AWS in Italy, Azure in Norway, Google Cloud in Indonesia), so use the one that works.
  • Benefit from portability
    • Migrate apps from one cloud to addition in any situation.

Many developer teams are already using single-cloud clusters; multi-cloud clusters are what’s new. A single-cloud array enables connected backups, automatic data tiering, and workload isolation. Multi-cloud clusters on MongoDB Atlas do all that, plus data administration and resiliency across clouds. 

The secret ‘data sharing’ weapon 

With multi-cloud clusters, there’s a tight alignment amid the assorted cloud platforms, so you can use the app-building tools you want and shift workloads as you see fit. And you can do that after adding data administration complexity.

Maybe you don’t need to run workloads across assorted public clouds right now — not anybody does. But with multi-cloud clusters, you can rest easier alive that cross-cloud clearing is now a simple option if you need it. It’s only a matter of time before most devs do. 

This commodity is brought to you by MongoDB.