Amazon API Gateway vs. Cleo Integration Cloud

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

CLEO Integration Cloud is well suited in any environment where you need to move and translate business data from one format to another or multiple other formats. It is very well suited to replace existing EDI systems that are cumbersome, are a lot of work to add new mappings (add customers for example), or where the support is lousy and you are constantly creating support tickets to try to resolve issues. It just works very well and is constantly improving including keeping up to changes made by various services such as Shopify.

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

• A great platform perfectly integrated with the rest of the company's software.
• Detailed design with simple and easy access from anywhere to our information.
• Multi-location and multi-device access.
• We save on hardware, software and maintenance, by minimizing the user's need for powerful equipment and the programs in charge of managing and configuring them, reducing the investment in their acquisition.
• Cleo integration is in charge of technical maintenance and updates.

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

• A fully functional help manual would be good. Some topics have no help at all, "envelopeassemblybycontext" for instance.
• A needed feature is to be able to sort files by either file type (FM, RS, BPS) or by filename. Some of our projects have almost a hundred files.
• Better, more descriptive error messages. Sometimes a ruleset or process fails and the error message is not helpful.

Incentivized

It is a great product very reliable and stable for connecting various aws services like we connected with lambda function and it is working very well, never faced any issue after the setup. It also saves out lots of money as well as time after we implemented the automatic ec2 server recovery system

Incentivized

Ease in understanding and setup.

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

Great data manager in the cloud, at a competitive price, backed by a great company and great professionals.

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

Before choosing a solution, we did a detailed analysis of cost, performance, scaling and support. Cleo checked all the right boxes and we have been very satisfied with our choice.

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

• We have easily improved our EDI tenfold (or more) as far as ease of adding new customers for example
• We have saved a ton of money by reducing chargebacks for missing ASNs for example
• We have improved customer scorecards where they measure our EDI performance such as one large brand name customer we sell wholesale to who originally scored us around 28% and after implementing CLEO we quickly went to a 96%+ score.

Incentivized