DataStax

<p><em>This is an excerpt from the Gartner&nbsp;report "The Future Of Cloud Data Management Is Multicloud" which delves into how data&nbsp;and analytics leaders will&nbsp;prepare for a multicloud and intercloud world.</em></p>

<hr />
<h2>Developing a Multicloud and Intercloud Strategy</h2>

<p>Multicloud means a given service can be operated on more than one cloud (see Note 1). For example, a data integration service can operate on two or more cloud infrastructure offerings. Multicloud is important for use cases where you are procuring cloud services and you want to ensure that offering works on different cloud platforms.</p>

<p>Intercloud means that integration has to take place between two services, with each service on a different cloud infrastructure. Intercloud is important for use cases where you are seeking to integrate data and analytics workflow across different services/clouds.</p>

<p>Developing a sound multicloud and intercloud data management strategy requires an understanding of the technology implications and associated challenges of each style of cloud deployment. The following research provides a solid grounding in the multicloud/intercloud problem space.</p>

<h3>“Technology Insight for Multicloud Computing”</h3>

<p>Most organizations will use more than one public cloud provider. Enterprise architecture and technology innovation leaders must select the multicloud strategy that best fits their business needs.</p>

<h3>“Multicloud: Why It Matters”</h3>

<p>A small group of megavendors dominates public cloud markets, which restricts new entrants’ ability to compete. To maximize available cloud opportunity, technology general managers must embrace and invest in multicloud.</p>

<h3>“Are You Ready for Multicloud and Intercloud Data Management?”</h3>

<p>The increased adoption of multicloud and intercloud deployments in support of data management solutions has important implications for data and analytics strategies. Data and analytics leaders must prepare for these impacts now in order to ensure optimal use of cloud resources.</p>

<h2>Data Integration in a Hybrid and Multicloud/Intercloud Data Landscape</h2>

<p>When data is split between multiple deployment environments, effective data integration becomes critical. The following research describes the hybrid cloud world, and presents comprehensive strategies to address data integration within it.</p>

<h3>“3 Ways That Hybrid Cloud for DBMS Will Drive Your Data Management Strategy”</h3>

<p>The majority of enterprises using cloud will be living in a hybrid deployment world for the foreseeable future. Data and analytics leaders must understand the risks and benefits in using the primary scenarios for hybrid cloud DBMS, and how these risks and benefits align with core use cases and architectures.</p>

<h3>“‘Unlearn’ Existing Practices for Success in Multicloud and Hybrid Data Integration”</h3>

<p>Data and analytics leaders must “unlearn” postimplementation data integration practices in order to succeed in multicloud or cloud and on-premises hybrid environments. Distributed data requires distributed integration that uses a combination of design approaches.</p>

<h3>“How to Architect a Multicloud-Capable Hybrid Integration Platform”</h3>

<p>As more applications and data move to the cloud, application leaders face increasingly complex integration requirements: within the same cloud, across different clouds and with on-premises endpoints. It has become crucial to support these diverse topologies in your hybrid integration platform strategy.&nbsp;</p>

<h3>Acronym Key and Glossary Terms</h3>

<div class="zdb-database-table">
<table>
	<tbody>
		<tr>
			<td>CSB</td>
			<td>
			<div>cloud service brokerage</div>
			</td>
		</tr>
		<tr>
			<td>IaaS</td>
			<td>
			<div>infrastructure as a service</div>
			</td>
		</tr>
		<tr>
			<td>PaaS</td>
			<td>
			<div>platform as a service</div>
			</td>
		</tr>
	</tbody>
</table>
</div>

<h3>Evidence</h3>

<p><sup>1&nbsp;</sup>Gartner’s Cloud Study 2018 (P-18029 Cloud Adoption). The survey was conducted online by an external partner, from October through November 2018. The full study surveyed 1,200 individuals. Of those surveyed, 628 reported that their organization was using the public cloud; and 507 of those respondents reported using more than one public cloud provider.</p>

<p><em>Results of this study do not represent “global” findings, or the market as a whole, but are a simple average of results for the targeted countries covered in this survey.&nbsp;</em></p>

<p>Note 1</p>

<h2>Hybrid Cloud, Multicloud and Intercloud Taxonomy</h2>

<p>There is a lack of clarity in the market around the definition and meaning of these terms. Vendors will often refer to their product as “multicloud” — by which they mean it runs on more than one cloud. Gartner accepts this definition, but finds it incomplete. Below, we articulate a full taxonomy for hybrid cloud, multicloud and intercloud architectures.</p>

<ul>
	<li>Hybrid Cloud — Refers to implementations that span on-premises and cloud deployments. In “<a href="https://www.gartner.com/en/documents/3877665/3-ways-that-hybrid-cloud-for-dbms-will-drive-your-data-m">3 Ways That Hybrid Cloud for DBMS Will Drive Your Data Management Strategy</a>,” we further define the subcases of:

	<ul>
		<li>Architecture Spanning Hybrid Cloud — Where components of a single logical deployment span on-premises and cloud.</li>
		<li>Use-Case-Specific Hybrid Cloud — Where different components are segmented by their development life cycle function (for example, development, test and production).</li>
	</ul>
	</li>
	<li>Multicloud — Where a service or product runs on the infrastructure of more than one cloud service provider, and may also run on-premises.</li>
	<li>Intercloud — Where data is integrated or exchanged between cloud service providers as part of a logical application deployment.</li>
</ul>

<p>These definitions can also be combined; for example:</p>

<ul>
	<li>Architecture Spanning Intercloud — would refer to a logical deployment of a single application — where components were deployed on more than one cloud and regularly exchanged data between the clouds.</li>
	<li>Use-Case-Specific Multicloud — would mean that a development environment was deployed in one cloud, and a production environment was deployed in another cloud.</li>
</ul>

<p>However, you could not have a “use-case-specific intercloud,” because data is not exchanged actively between the environments in a use-case-specific scenario.</p>

<hr />
<p><em>Thanks for reading this excerpt from&nbsp;the Gartner&nbsp;report "The Future Of Cloud Data Management Is Multicloud,"&nbsp;tune in next week when we'll release another excerpt or&nbsp;<a href="https://www.datastax.com/resources/report/gartner-report-future-cloud-data-management-multicloud">click here</a>&nbsp;to download the full asset.</em>&nbsp;</p>


Why a Multicloud and Intercloud Strategy is Necessary

DataStax

Discover more

Share

Share

Developing a Multicloud and Intercloud Strategy

“Technology Insight for Multicloud Computing”

“Multicloud: Why It Matters”

“Are You Ready for Multicloud and Intercloud Data Management?”

Data Integration in a Hybrid and Multicloud/Intercloud Data Landscape

“3 Ways That Hybrid Cloud for DBMS Will Drive Your Data Management Strategy”

“‘Unlearn’ Existing Practices for Success in Multicloud and Hybrid Data Integration”

“How to Architect a Multicloud-Capable Hybrid Integration Platform”

Acronym Key and Glossary Terms

Evidence

Hybrid Cloud, Multicloud and Intercloud Taxonomy

More Company

DataStax Acquires Langflow to Accelerate Generative AI Development

The Top 5 DataStax Stories from 2023

2023 Recap: Data = AI

DataStax Astra DB Nabs Three Prestigious 2023 TrustRadius “Best of” Awards, Dominates the Vector Databases Category

One-stop Data API for Production GenAI