September 7, 2017 | Written by: Chris Schmitt
Share this post:
Let’s say you suddenly have the power to clone yourself. How many of you would it take to tackle all of your work on any given day? Two? Three? Four? Twelve?
If this sounds like a familiar scenario, you probably remember the movie “Multiplicity” starring Michael Keaton (and Michael Keaton and Michael Keaton) as Doug Kinney, a construction worker whose demanding job is getting in the way of his family life. While working on a construction project at a science facility he is offered what appears to be the perfect solution: clone himself.
Initially, he creates a clone (Doug Number 2) to take his place at work so he can spend more time with his family. But when that isn’t enough, he creates a second clone (Doug Number 3) to help around the house. Then the clones start creating their own clones (Doug Number 4) to help share some of the workload with less-than-stellar results. You know how when you make a copy of a copy, it’s not as sharp as the original. What started as a way to simplify, reduce his workload and accomplish things faster just made his life more complex—and not as sharp.
This very well could describe your current cloud environment. Business leaders are making technology adoption decisions with less involvement of central IT. This has led to the explosion of new endpoints like mobile, social and the Internet of Things. The resulting complexity drives the need for additional custom applications. Even though all of this has been done in the name of speed and agility, it has led to a huge increase in decentralized deployments across on-premises and multicloud environments. How many different business initiated-clouds do you even have running? One. Two. Three. Maybe twelve.
The sprawling cloud environment has necessitated a shift in the role of centralized IT teams to evolve from a controlling role to an integrating role. Because no matter where these applications are located and who owns them, they all need to work together. The name of the game in a hybrid world is interoperability.
Hybrid integration, a combination of technologies, tools and services, ensures the ability to connect any application regardless of location and architecture. But moving to a hybrid integration approach can be challenging for some organizations. So we brought in our friends at IDC to help define the top five triggers that force organizations to move to a hybrid integration approach.
Over the next few weeks, I will share key findings from the IDC report, “The Urgent Need for Hybrid Integration.” Upcoming posts will explore how organizations are responding to changing integration requirements by focusing on:
- The need to integrate cloud and on-premises applications
- Mobile enablement of applications and digital services
- Proliferation of representational state transfer (REST) APIs and the need to manage their lifecycles
- Supporting analytics-driven applications
- End-user self-service integration
Your new normal is a combination of multicloud and on-premises environments that all need to connect. How successfully you can make that happen will define your success.
If you want to get a head start, download the IDC Report, “The Urgent Need for Hybrid Integration” or go to ibm.com/integration to learn more about only-from-IBM solutions for hybrid cloud integration.