Share this post:

Recently, we unveiled IBM Cloud Private. It’s been exciting to see the impact that this technology has had on our clients’ businesses. Many immediately understood the value of the offering. But for those who are still evaluating their cloud adoption model, there are still some misconceptions of why a private cloud may be needed. If you’re only starting to explore the options of private cloud, I’ll help clarify a few common misunderstandings.

4 commons myths about private cloud

  1. Organizations need to choose between public and private cloud: After working with customers on their cloud strategy for many years, one thing that becomes clear is there is no one cloud solution for every customer. In fact, often the same customer will need different solutions for varying workloads. Many businesses choose a private cloud to keep sensitive workloads behind the firewall, while also taking advantages of both public cloud and on-premise solutions for other business needs. The beauty of a hybrid cloud strategy is your enterprise can reap the benefits of multiple approaches and integrate them smoothly. Many organizations start with one deployment model, and move the workload to another model as their business needs change.
  2. Private cloud means no shared infrastructure: When many hear the word “private” they think on-premise. There is still some market confusion over the term, but the most meaningful distinction between private and public cloud is whether or not the customer can control the underlying infrastructure and the software deployed on top of that infrastructure. They may choose to manage the infrastructure themselves, or they may choose to outsource that management. But the basic premise for a private cloud is that the customer has a high level of control over the configurations and security of the entire environment – from infrastructure to data to applications.  For example, IBM has a VMware solution that runs an IaaS based private cloud on a shared infrastructure, while IBM Cloud Private is a PaaS solution which runs on the client’s infrastructure. Either can be considered private cloud, so long as the client maintains privacy and control.
  3. Cloud adoption means losing existing investments: One concern that managers have about cloud migration is that existing training and investments will be lost with the new technology. This concern is understandable, but the right cloud solution can help teams tackle this issue by bridging to cloud at a rate and pace which makes sense for their business. For example, IBM Cloud Private includes middleware solutions such as MQ and Db2 running on x86 or Power Systems to help customers take advantage of cloud benefits without losing existing investments in software, HW systems, and skill sets. Modernizing applications and operational processes onto the cloud, while also developing new cloud native projects, is often the perfect balance for enterprises.
  4. Private cloud sacrifices flexibility: This couldn’t be further from the truth. Private cloud is an extremely flexible option. The right cloud offering is a powerful solution for protecting data, managing existing investments, meeting regulatory requirements, leveraging an ecosystem of public cloud and industry services and building cloud native apps. Additionally, IBM Cloud Private allows clients to use a combination of open source resources, IBM tools and their own applications to get the best of each.

I hope these points were useful for you in your cloud journey.  In the next post, we’ll help explain what an organization should look for in a private cloud provider. To learn more about IBM Cloud Private, visit the official IBM Cloud Private page.
















#IBMCloud,#awvi

via Cloud computing news https://ibm.co/2cigQr9

December 11, 2017 at 08:42PM