Hybrid Integration by Nature and Not by Construction
Lots of people are talking about the Hybrid Integration Platform. What if it was software that was Hybrid by nature?
Join the DZone community and get the full member experience.Join For Free
In the field of integration, there is a lot of talk about the Hybrid Integration Platform. It consists of having a suite of software, which, put together, allows managing the integration of on-premise software with cloud software. However, there is a subject that is rarely mentioned: The hybridization of the components themselves!
A world without hybrid components
In a world without hybrid components, to integrate your on-premise legacy with your SaaS and PaaS applications, you will typically have the following architecture:
A Legacy exposed by an ESB or directly exposing REST APIs
A Gateway API that will expose the Rest API
An iPaaS that will consume your API from Legacy and that will work with "Cloud" APIs.
All this is very good; it works, but clearly, if you have a hybrid service bus, your API Manager will potentially not be useful for much. Indeed, how many APIs or SOAP web services are actually reused? How have you designed your API to be reusable, but in fact, you won’t reuse it? How much time have you wasted developing the API? What loss of performance has there been following the mandatory passage through the API Manager?
All this is to say that no, an API Manager is not "the" solution to all your problems, but a kind of second-best; a necessary step to connect your systems between them.
A world with a Hybrid component
If now your bus is itself a Hybrid — let's call it an iPaaS Hybrid — what will your architecture look like? To this typically:
An iPaaS that connects to your on-premise legacy but also to your cloud applications
And that's all!
We can see the time savings in development but also in terms of performance. Of course, we lose the ability to reuse, but if that's your real wish, then do it! We would even call this an API approach! :) However, if you connect two systems together, you are not necessarily in an API approach!
And a world with a Hybrid Manager API?
Well, it's not bad at all, actually! Because one of the questions you may ask yourself when you make an API is who will call your API? If it comes from the cloud, should I put my API on the cloud and vice versa for on-premise?
So, if we say that any component must become hybrid, we would then be able to send files without constraint, use Data Virtualization with no other question than to connect to data sources, and ETL/CDC/ELT would be pure ease! It is towards this state that I hope the world of integration will evolve, a seamless world!
Opinions expressed by DZone contributors are their own.