Amazon API Gateway vs. Filestack

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

The integration is airy and the performance is amazing. Initially, we used our photo file uploader and it worked, but as our needs grew the developmental effort to support new needs took a lifetime. As a development manager, this was a big red flag because uploading files had become a hindrance and time-consuming away from other purposes.

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

• Digital Asset Management
• Seamless Integration into WYSIWYG Editor
• Asset Size Restrictions

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

• Tricky to navigate at first
• No dashboard for the file conversion
• Their script download used to fail on occasion

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

Ease of integration [was] that we had developers who were familiar with implementing Filestack. It also decreased the dependency and load of our Developers since the implementation instructions are fairly straightforward. Filestack is excellent at what it does (asset management) and Cloudinary/Akamai is primarily used to serve content and decrease latency as CDNs.

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

• Ease of implementation
• Software works flawlessly
• Multiple Gateways

Incentivized