Is really Open Studio for ESB like Open Studio for DI++ ?
Hello everyone,
I've always been used to using Open Studio for DI. However, I might have a need to develop REST API for instance. So, I should use Open Studio for ESB.
I wonder if it's effective to use DI and ESB separately, and if every DI features and components are in ESB ?
In this case I should export my project from DI, and import into ESB.
I've always preferred the ESB product to the DI product. Since I work at Talend, I have access to the Data Fabric product, so it has been a while since I've relied upon the Open Studio product. However, I cannot name a single thing that I was missing in ESB when I used that instead of DI. Only additional stuff. Web Services can be built in ESB and it essentially works just like DI. The only area that is different (and it is very different) is the routes. Talend Routes are essentially just like Apache Camel routes. They are built in a different way and require a deeper understanding of Java and Apache Camel. They can be incredibly useful when you understand them though. The DI stuff will work in the same way.
I've always preferred the ESB product to the DI product. Since I work at Talend, I have access to the Data Fabric product, so it has been a while since I've relied upon the Open Studio product. However, I cannot name a single thing that I was missing in ESB when I used that instead of DI. Only additional stuff. Web Services can be built in ESB and it essentially works just like DI. The only area that is different (and it is very different) is the routes. Talend Routes are essentially just like Apache Camel routes. They are built in a different way and require a deeper understanding of Java and Apache Camel. They can be incredibly useful when you understand them though. The DI stuff will work in the same way.
