How Hybrid Do You Need To Be?

Cloud is moving forward so fast that most hybrid cloud platforms and tools will probably be outdated before you get them up and running. Choose carefully what you need as core features, and plug into the knowledge of a company like Nordcloud.

Everybody appreciates the agility and elasticity of the public cloud, however, there are also large amounts of legacy apps that simply don’t move easily to the public cloud. This means that up until now, the Hybrid Cloud choir has been singing their ‘happily ever after’ song.

Unfortunately, this hybrid cloud choir has largely become led by the vendors who have the most to lose and use this as a way to stall things. So let’s break down what you actually need and what could be seen as a colossal waste of time and money.

The Good

These activities will benefit you in the long-term

  • Common security and governance framework. Regardless of the clouds you use, you should enforce the same security and governance principles.
  • Every cloud is a silo so if you want to have an end to end understanding of your IT, you need a tool that monitors across all clouds. That also goes for all core ITBM tools.
  • A light portal will help end users by collecting the different clouds under one interface and access control. But keep it light as most cloud usage is through automated API calls, not through a manual portal.
  • Any activity that gets your apps to run on software-defined infra, including containers, network virtualization etc.

The Bad

  • Any investment around workload movement between clouds (beyond virtualising and using containers) can waste you both money and time. Legacy app workload movement between clouds is not really achievable in the first place and you need to consider what is the real benefit (and your appetite to invest) of the ability to move between clouds. You’re much better off having a multi-cloud procurement approach where the threat of other clouds keeps the prices in check. You can then implement any technical cloud brokerage, workload movement solution etc.
  • Private cloud – yes it would be wonderful to have the same experience with ‘on-prem’ that you have in public clouds, but the cost of achieving this is just not worth it, especially considering that you have 15% less apps needing it every year. AWS and Azure implement hundreds of new services every year. How would you keep up with that in your own private cloud?
  • Inertia is probably the worst consequence of a hybrid strategy. Any investment in hybrid technologies is money off your budget which could be used to innovate, by modernising and building new apps. In short, money that is actually used to improve business. Secondly, any investment needs usage and you urgently need to prove that this is a good investment leading to suboptimal workload placement. Thirdly, you have a large, complex platform that is not keeping up with the demand for new services, needs constant upgrades and doesn’t scale when needed.

The Bottom Line Of Hybrid Cloud

At the end of the day, this is all about focus. Hybrid cloud strategy means that you invest into 3 areas – implementing and improving your private cloud, your cloud brokerage platform, and increasing your usage of public clouds. How much more could you achieve with the money if you just focus on one of them?

Cloud is moving forward so fast that most hybrid cloud platforms and tools will probably be outdated before you get them up and running. Choose carefully what you need as core features, and plug into the knowledge of a company like Nordcloud who can help you to choose the right tools whilst also keeping them updated.

Blog

Part 1 – GCP Networking Philosophy

When working with cloud architecture, it's important to see the world from different perspectives.

Blog

Part 2 – Two Different Types of GCP Network Designs

When designing your network in GCP, you need to decide if you want to go fully GCP native or use...

Blog

Accelerate resource tagging with PowerShell — Microsoft Azure Tag Report

Once, I prepared this script to quickly tag many resources deployed on the Microsoft Azure platform. There are many ways...

Get in Touch

Let’s discuss how we can help with your cloud journey. Our experts are standing by to talk about your migration, modernisation, development and skills challenges.








    The myth of the workload movement

    CATEGORIES

    Blog

    Before you invest your time and money into hybrid cloud, you should understand the realities in workload movement between clouds. Who wouldn’t want to be able to move apps between clouds based on your own needs, not to mention that you wouldn’t need to do a single migration project again.

    So you’ve moved your apps to containers, invested in a Cloud Management Platform (the brokerage engine for your clouds) and you’re all set.

    Unfortunately, no. Even if you would have the technical possibility to move workloads, there are few critical topics that render it unusable in real life.

    Let’s start with some basic facts:

    • Your existing apps are not built with workload movement in mind.
    • Even the new applications need to be designed and built with workload movement in mind in order for that to work. And that comes with a cost.
    • Every cloud is a silo with its own features, tweaks, cost optimization options etc.

    So what are the difficulties with workload movement?

    First is your deployment processes – a pretty normal step in any change (including migration) is to plan, design, implement and validate. For you to benefit from workload movement, you need to minimize these steps. Let’s assume you get a 10% cost saving by moving to a new cloud. How much of the design, validation and coordination work can you fund with that? If you follow a DevOps process for your cloud native app, this is probably doable, but for your other apps this is big culture change or you’ll burn most of your savings in the project whilst performing the change.

    Data – most apps you consider to be a candidate for workload movement probably contain data, and lots of it. The data synchronization brings two challenges you need to tackle – data consistency and data transfer time. If data consistency is crucial for you, you first need to move every single byte of data before switching over, which means that at some point you need to stop taking new data in, sync the data and then start taking data in again. This probably means a production break, which means planning and execution work, which means costs and delays. The second issue in some cases is simply the time it takes to sync data. It can take weeks and can require separate physical swing boxes.

    Platform dependencies – we’re all supposed to use APIs that hide underlying technical implementation and thus make us less platform dependent. But the reality is that most of the APIs we use are unique, and those are the biggest competitive advantage of the cloud provider. You can write totally platform agnostic code, (that was the big promise from Java from about 20 years ago) but for various good reasons (time to market, cost, laziness etc) we tend to use platform specific features and functionalities. The rise of PaaS will further increase your platform dependency.

    We can be honest with ourselves and say that time and cost pressure in most apps dev project override any TCO, reusability and workload movement ambitions.

    They are not alike – even if you have the same stack at both ends (regardless if it’s Microsoft, Vmware or OpenStack based) they are not the same. A cloud consists of a large number of components and having the same versions of each component on both ends is not going to work. VM sizes are also different. Some workloads will move just fine, some not, but you need to plan and test.

    Skills – we’re in a global war for talent. Most companies have difficulties recruiting and developing skills for one cloud platform, so it’s tough finding people who not only can handle containers on multiple clouds but also do that on scale.

    Cost optimization – private cloud and public cloud have very different cost drivers and optimization possibilities. Your cost optimization options include long-term commitments, licence cost savings, right-sizing etc, all reducing your ability to move workloads to a different place.

    Getting your priorities right

    Enabling true cloud brokerage and workload movement code can be achieved but at a high cost. In most cases, the reality is that workload movement requires a separate project that creates costs, delays and ultimately takes away real appetite to move the workload. At the end of the day, it’s all about your company’s priorities. Do you get the competitive benefit from cloud brokerage, or maybe using the same money to bring new services faster to market? Workload movement is a nice thing to have but has a little positive effect on your TCO. In this case, time to market and your apps dev cost are much bigger drivers.

    • To find out more about Hybrid cloud, read my blog ‘How Hybrid do you need to be’  here 
    • Norcloud have been placed on the Gartner Magic Quadrant for the MSP journey for the second year, read more about it here

    Blog

    Starter for 10: Meet Jonna Iljin, Nordcloud’s Head of Design

    When people start working with Nordcloud, they generally comment on 2 things. First, how friendly and knowledgeable everyone is. Second,...

    Blog

    Building better SaaS products with UX Writing (Part 3)

    UX writers are not omniscient, and it’s best for them to resist the temptation to work in isolation, just as...

    Blog

    Building better SaaS products with UX Writing (Part 2)

    The main purpose of UX writing is to ensure that the people who use any software have a positive experience.

    Get in Touch

    Let’s discuss how we can help with your cloud journey. Our experts are standing by to talk about your migration, modernisation, development and skills challenges.








      How hybrid do you need to be?

      CATEGORIES

      Blog

      Everybody appreciates the agility and elasticity of the public cloud, however, there are also large amounts of legacy apps that simply don’t move easily to the public cloud. This means that up until now, the Hybrid Cloud choir has been singing their ‘happily ever after’ song.

      Unfortunately, this hybrid cloud choir has largely become led by the vendors who have the most to lose and use this as a way to stall things. So let’s break down what you actually need and what could be seen as a colossal waste of time and money.

      The good

      These activities will benefit you in the long-term

      • Common security and governance framework. Regardless of the clouds you use, you should enforce the same security and governance principles.
      • Every cloud is a silo so if you want to have an end to end understanding of your IT, you need a tool that monitors across all clouds. That also goes for all core ITBM tools.
      • A light portal will help end users by collecting the different clouds under one interface and access control. But keep it light as most cloud usage is through automated API calls, not through a manual portal.
      • Any activity that gets your apps to run on software-defined infra, including containers, network virtualization etc.

      The bad

      • Any investment around workload movement between clouds (beyond virtualising and using containers) can waste you both money and time. Legacy app workload movement between clouds is not really achievable in the first place and you need to consider what is the real benefit (and your appetite to invest) of the ability to move between clouds. You’re much better off having a multi-cloud procurement approach where the threat of other clouds keeps the prices in check. You can then implement any technical cloud brokerage, workload movement solution etc.
      • Private cloud – yes it would be wonderful to have the same experience with ‘on-prem’ that you have in public clouds, but the cost of achieving this is just not worth it, especially considering that you have 15% less apps needing it every year. AWS and Azure implement hundreds of new services every year. How would you keep up with that in your own private cloud?
      • Inertia is probably the worst consequence of a hybrid strategy. Any investment in hybrid technologies is money off your budget which could be used to innovate, by modernising and building new apps. In short, money that is actually used to improve business. Secondly, any investment needs usage and you urgently need to prove that this is a good investment leading to suboptimal workload placement. Thirdly, you have a large, complex platform that is not keeping up with the demand for new services, needs constant upgrades and doesn’t scale when needed.

      The bottom line of hybrid cloud

      At the end of the day, this is all about focus. Hybrid cloud strategy means that you invest into 3 areas – implementing and improving your private cloud, your cloud brokerage platform, and increasing your usage of public clouds. How much more could you achieve with the money if you just focus on one of them?

      Cloud is moving forward so fast that most hybrid cloud platforms and tools will probably be outdated before you get them up and running. Choose carefully what you need as core features, and plug into the knowledge of a company like Nordcloud who can help you to choose the right tools whilst also keeping them updated.

      Blog

      Starter for 10: Meet Jonna Iljin, Nordcloud’s Head of Design

      When people start working with Nordcloud, they generally comment on 2 things. First, how friendly and knowledgeable everyone is. Second,...

      Blog

      Building better SaaS products with UX Writing (Part 3)

      UX writers are not omniscient, and it’s best for them to resist the temptation to work in isolation, just as...

      Blog

      Building better SaaS products with UX Writing (Part 2)

      The main purpose of UX writing is to ensure that the people who use any software have a positive experience.

      Get in Touch

      Let’s discuss how we can help with your cloud journey. Our experts are standing by to talk about your migration, modernisation, development and skills challenges.