Cloud Pak for Integration

 View Only

Applying Heisenberg's Uncertainty Principle to understand the need for Cloud Pak for Integration

By Leif Davidsen posted Fri March 05, 2021 02:15 PM


Sometimes is only takes a small step to change the world. But that small step is likely the outcome of a longer journey. The Heisenberg’s Uncertainty Principle states (roughly) you can either know where something is, but not where it’s going. While it is designed to apply to wave equations, you can try to apply it to other aspects of life.

 Heisenberg not Heisenberg

Let’s start with the car market. Today all around the world there is a change going on. Reading the statistics, the European market today shows Petrol/Gas cars with 52%, Diesel with 30%, Hybrid at 10% and Electric at 6%. We therefore know where something is from these numbers, but not where it is going. Indeed, you might say this is good news for the Petrol and Diesel car market.

However, if you look at a different set of statistics, you see a different story. You see where the market is going. New car sales were 80% electric cars. We are seeing a huge shift. Taking a snapshot from one set of information isn’t enough. Bear in mind the car market can’t completely change overnight. People might run their cars for 5-10 years between new updates.


Now let’s consider the market for IT infrastructure and specifically integration. What are customers using today? The vast majority of businesses today run most of their infrastructure in their own data center. They run on bare-metal, or VMs. And their applications are probably complex, tightly coupled with where and how they are installed and deployed. Many applications and integrations would be around 5-10 years old, and if the business was advanced enough at the time, the integration architecture would be built to use SOA principles and connect together using an ESB.

 SOA reference architecture

If we looked at the integration market today, we would certainly see this as an endorsement of SOA and ESBs as the dominant way to connect applications. But let’s switch views now. Let’s consider what happens when you want to make a change, just like when you make a change of car, you are thinking about what’s right for now, and for the future. What would you consider? You want to think about using this as an opportunity to take advantage of the latest in new technologies. For integration that is exploiting the capabilities of Kubernetes and the power of DevOps to make your business more agile than ever.

For applications using integration, by being forward looking in your choices you can exploit APIs to engage with customers while still seamlessly connecting with back-end systems and data. And you can update your systems of record securely and at scale, while ensuring that updates trigger new information flows rapidly throughout your business.

 Cloud Pak for Integration Architecture

Just as today’s electric cars don’t make you learn new skills in driving, Cloud Pak for Integration from IBM builds on your existing integration and application skills. It can exploit what you have previously learned from SOA principles and deploying ESBs, but it represents a change to a completely modern integration creation, deployment, operation and maintenance approach.

 Drive new engagement models

If you are a business user of integration reading this, I don’t know exactly where you are today, but I have a good idea of where you are going. Because the best choice for integration is IBM’s Cloud Pak for Integration. Exploit the power of Red Hat OpenShift, along with multi-style integration enhanced by automation and smart connectors.


You might look at your old car and think it’s time to upgrade. You need to look at your integration deployment today and think if it might be time for Cloud Pak for Integration. Check out the demos today