Talend ESB vs. WebOTX Enterprise Service Bus

Recommended for:

1. Multiple systems to interface for a task in the company (example: to sell an item your POS must communicate with the inventory software, then to accounting, then to service, etc).
2. When a task must bring information from several external services.
3. When you have to deal with multiple APIs.

Not recommended for:

1. Data transformation (although Talend has a software for that that works with Talend ESB)

Incentivized

• Up to 900 connectors included in the license with no extra cost
• Graphical UI to develop the Web Services
• You can begin with the community version to evaluate or start implementing a very uncomplicated ESB
• The Talend ESB Admin Control is very powerful with dashboards and reports to keep your IF working smoothly

Incentivized

• You have to log in to each module separately
• 900 connectors is a lot, but if you have a custom app to interface, you have to develop your connector

Incentivized

• First, it is a lot of cheaper than the closest competitor.
• Second, Talend ESB is in the same league as other stronger brands.
• Third, the functions and modules are a 360 solution to implement an ESB.

Talend has a different approach to license since it is based on programmers and run times, not to users of cores.

Incentivized

• Considerably cheaper than oracle service bus
• As I said before, you can run a POC using the community version of Talend Studio.
• Built from Open Source/ well-proven technologies, and a big community to support those technologies.

Incentivized