Amazon API Gateway vs. Talend ESB

Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.

Incentivized

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

• API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway.
• API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting).
• API Gateway's pricing can be very attractive for services that are accessed infrequently.

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

• Client certificates are troublesome when trying to attach them to API GW stages.
• Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB.
• Creating internal/private APIs, particularly with custom domains, can be unintuitive.

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

We always had a great experience with the AWS support team. They were always on time and very dependable. It was a good partnership while we worked to resolve our issues.

Incentivized

When we tested Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up choosing to continue using AWS products. This so as not to run the risk of increasing latency in accesses, and of some functionality not working, due to being developed yet.

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

• ROI is negative, you need either to hire them to work with you or spend days/weeks to figure out issues.
• For some of the projects in the end it is not worth it, it is just a "buzz" to use serverless but not practical.
• Service is easy to set up authorization and it is easy to manage.

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