3 multicloud architecture patterns cloud pros should understand

Multicloud is one of those deployment models that most enterprises already use but do so without having purposefully intended to move to multicloud. In other words, multicloud architecture by accident.

I’m noticing some emerging patterns around the purposeful use of multicloud and its benefits. These architectures are derived from the business value of leveraging multicloud, not the result of random decisions that result in multiclouds. There is a huge difference.

Here are three emerging multicloud architectures and what you should know about them:

Data-oriented multicloud architectures. Multicloud typically means that the data is coupled to the cloud provider running the applications. Thus, SQL Server may be bound to Azure-based applications, whereas MySQL may be bound to AWS-based applications.

This is not optimal, considering that the public clouds become islands unto themselves as far as data goes, not working or playing well with other databases and applications that exist on other public clouds in a multicloud architecture.

A data-oriented multicloud means that the focus is one common data source shared among the different public clouds. There is a single source of truth for core data, such as customers and sales.

Copyright © 2020 IDG Communications, Inc.

Source link