Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

3 Pitfalls Everyone Should Avoid with Hybrid Multi-cloud (Part 3)

DZone's Guide to

3 Pitfalls Everyone Should Avoid with Hybrid Multi-cloud (Part 3)

Dig through the hype of cloud and get to the critical questions with the third part of this series explaining what you should and shouldn't move to the cloud.

· Cloud Zone ·
Free Resource

Download Microservices for Java Developers: A hands-on introduction to frameworks and containers. Brought to you in partnership with Red Hat.

The daily cloud hype is all around you, yet there are three pitfalls everyone should avoid.

From cloud, to hybrid cloud, to hybrid multi-cloud, you’re told this is the way to ensure a digital future for your business. These choices you’ve got to make don’t preclude the daily work of enhancing your customer's experience and agile delivery of those applications.

Let's take a journey, looking closely at what hybrid multi-cloud means for your business. Let's examine the decisions being made when delivering applications and dealing with legacy applications. Likely these are some of the most important resources to your business.

This article highlights three pitfalls everyone should be aware of when transitioning into hybrid multi-cloud environments. It's based on experiences from interactions with organizations working to conquer hybrid multi-cloud while delivering their solutions.

In part one, we covered the basic definitions to level the playing field. We outlined our views on hybrid cloud and multi-cloud, making sure to show the dividing lines between the two. This set the stage for part two, where the first pitfall discussed why cost is not always the obvious motivator for moving into the cloud.

In part three, it's time for technology and looking at the question of whether it's a good plan moving all workloads into the cloud.

Everything's Better in the Cloud

three pitfallsThe second pitfall is about the misconception that everything will benefit from running in the cloud. All workloads are not equal and not all workloads moving into the cloud result in a measurable effect on the bottom line.

recent article stated, "Not all business applications should migrate to the cloud, and enterprises must determine which apps are best suited to a cloud environment." A hard fact that the utility company mentioned in part two of this series found out as labor cost estimations rose while trying to move applications into the cloud.

Discovering this was not a viable solution, the utility company backed up and re-evaluated their applications. Turns out, some application were not heavily used, and others had data ownership and compliance issues. Some of their applications were not certified for use in a cloud environment.

Sometimes it's not physically possible to run applications in the cloud, but other times it's not financially viable to run in the cloud.

Imagine a fictive online travel company. As their business grew, they expanded their hosting capacity on-premise eventually to over 40 thousand servers. It became a question of expanding their resources by purchasing a data center at a time, not a rack at a time. Their business consumes bandwidth at such volumes that cloud pricing models, based on bandwidth usage, remains prohibitive.

Why a Baseline?

Nothing is more important than having a thorough understanding of your application landscape, as the examples above show. Along with a good understanding of what applications need to migrate to the cloud, you also need to understand current IT environments, the present level of resources, and estimated costs for moving.

The current situation and performance requirements (network, storage, CPU, memory, application & infrastructure behavior under load, etc), called a baseline, gives you the tools to make the right decision.

If you’re running servers with single-digit CPU utilization due complex acquisition processes, then a cloud might be a great idea with on-demand resourcing. However, first ask these questions:

  • How long did this low utilization exist? 
  • Why wasn’t it caught earlier? 
  • Isn’t there a process or effective monitoring in place? 
  • Do you really need a cloud to fix this, or just a better process for both getting resources and managing said resources? 
  • Will you have a better process in the cloud?

Container Necessity

Many believe that you need containers to be successful in the cloud. The famous catchphrase sums it up nicely, "We crammed this monolith into a container and called it a microservice."

three pitfallsContainers are a means to an end, and using containers doesn’t mean your organization is capable of running maturely in the cloud. It's not about the technology involved, it's about applications that often were written in days gone by using dated technology. If you put a tire fire into a container and then put that container on a container platform (ship), it's still functionality that someone is using.

Is that fire now easier to extinguish? These container fires just create more challenges for your DevOps teams, who are already struggling to keep up with all the changes being pushed through an organization moving everything into the cloud.

Note, it’s not a default bad decision to move legacy workloads into the cloud, nor is it a bad idea to containerize them. It’s about weighing the benefits, the downside, assessing the options available and making the right choices for each of your workloads.

Pitfalls Everyone Should Avoid

In part four of this series, the third and final pitfall is presented. A pitfall that everyone should avoid with hybrid multi-cloud. Find out what the cloud means for your data.

Missing the start of this series? Just head on back and catch up with part 1.

Download Building Reactive Microservices in Java: Asynchronous and Event-Based Application Design. Brought to you in partnership with Red Hat

Topics:
cloud ,hybrid cloud ,hybrid ,multicloud ,hybrid multi cloud ,multicloud strategy ,pitfalls ,developers ,architects ,cio

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}