In Pokémon Go
, collecting Pokémon is just the beginning, you have to evolve it to the next level to stay in the game. Evolving a particular species of Pokémon gives more CP (Combat points) and HP (Hit points), so that it can be a valuable addition to your collection. To fight better, you need a stronger Pokémon. Same is the case for Enterprise Services Bus(ESB)
. Enterprises have spent years of building the best integration platform to bring their various systems(especially legacy ones) together. ESB is the heart of big enterprise’s SOA strategy. Enough time has been spent on collecting the Pokémon, isn’t time to evolve it?
ESBs that are being used today has matured over the years to keep up with the pace of evolution of fronts like web apps. And at the same time they didn’t leave the backs like legacies behind. Today we can integrate almost anything with everything. Most of the systems are loosely coupled and services are being reused to the maximum levels. The primary duties of ESB like integration issues are very well addressed today. Is that enough? Aren’t we being left behind in the cloud era?
Cloud era and the new challenges
There is no doubt about what ESB had contributed to the enterprises. But then, that was the need of the hour. Now the issues we face are very different. There is a huge gap between the development and operations teams. Though the enterprises are trying to close the gap by various collaboration mechanisms, the ultimate solution would be single team handling both development and operations. ESBs on the market pose a lot of challenges when we look out for the continuous delivery pipeline.
Another issue we face very often is infrastructure nightmare. When the code/solution moves from development to production, it passes through a lot of environments like dev, sit, uat and so. Most of the problems occur due to the mismatch in the versions of software and infra available in different environments. Moreover, by often looking outwards, integrating as many as systems, we end up building monolithic applications at our end. In the businesses like financial services where regulatory compliances change very often, updating the entire application even for a minor change makes no sense.
A way forward
ESB today is mostly being considered for its technical aspects, but it’s time that we look for functional capabilities too. With almost all the previous set goals being achieved, now is the time to move from cutting costs to bringing business. No ESB is not a solution, but an evolved one can be. An ESB that provides a good platform for Containers, Microservices
, can solve all the issues that I mentioned earlier. How can an ESB with all the above capabilities solve the next generation issues? That’s my next post!