How to deal with data in a multicloud environment

Follow these three best practices to keep the use of multiple databases across multiple clouds from confounding your deployments

Become An Insider

Sign up now and get FREE access to hundreds of Insider articles, guides, reviews, interviews, blogs, and other premium content. Learn more.

You are setting up a quick report around sales for the year, and it needs to use three separate databases. One is an object database running on Amazon Web Services. The second and third are relational databases running on Microsoft Azure.

You have a few issues to address in this multicloud scenario:

  • Finding the single source of truth among the three databases, such as customer information.
  • Dealing with the different data types and structures native to each database.
  • Dealing with complex security layers on each database and cloud provider.

The fact of the matter is that data is not centralized. Indeed, databases these days are purpose-built, and so you have different databases for analytics, operations, and multimedia management.

A multicloud approach brings an extra layer of complexity due to the fact that you have security at the database layer (such as encryption), at the platform/operating-system layer, and at the cloud layer.

Working with multiple databases on a single cloud is difficult enough, so just wait till you work with multiple databases across two or three clouds at the same time for the same application use cases! This is a wall that many enterprises are running into now, and it will get worse in 2019.

To continue reading this article register now