I have been using TOS_DI for the longest time. When I wanted to spin off a quick service, I saw TOS ESB, and saw the familiar DI perspective. I put in tRestRequest/ tRestResponse components and bam, my service was up and running.
I see that one can setup REST services using ROUTES also.
I am just trying to see if Routes can add any value to my current setup and learn more.
I could not find much documentation to answer above questions.
Any help is appreciated. Thank you
You can reuse your job in a route with cTalendJob component.
Routes are based on Enterprise Integration Patterns, you take benefits of the numerous camel parameters and connectivity, you can route to several recipients, add conditions, filtering, gather several data sources, developp in java with its librairies to do almost everything you want.
Jobs are more convenient for graphical design and integrationf of mapping between sources and output. They're usually used as ETL for batch and bulk data processing, routes a usually used for real-time transfer of smaller data sets.
you get benefits of all the EIPs. For routing, duplicating messages, scalability with ActiveMQ to transmit data between several routes (thus you can stop any one, the others will continue working, and MQ stores the messages, then the stopped route restarts and everything is OK with no human action. Very usefull).
You can also encode data for security reasons if you need.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Take a look at this technical overview video of Talend API Designer
Find out how to get started with APIs