Akamai API Gateway vs. Amazon API Gateway

Our well suited scenario is when working with high-traffic APIs. Akamai API Gateway's scalability and performance optimisation capabilities provide effective handling of huge volumes of API calls, guaranteeing users' best possible experience. One less appropriate scenario is that the price of Akamai API Gateway may be too high for organisations on a tight budget, particularly if they don't need all of the platform's capabilities.

Incentivized

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

• Graphically representation in GraphQL
• Scaling system
• DevOps management

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

• Improvements required to real-time monitoring tools, like more detailed alerting settings and advanced analytics dashboards, could offer more insight into API performance and security breaches.
• For less experienced users, setting up advanced security rules or personalising authentication procedures might be difficult and require deep technical expertise.
• Although it works well with a range of backend systems and protocols, it could be helpful to offer additional pre-configured connectors or easier integration choices for widely used services and platforms.

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

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

Akamai [API Gateway] helps better in terms of representation of graphQL and its consumption in monitoring system making a package for deployment speed with monitoring and scaling application with all services and utilizing most of a system without much knowledge of other aspects. Also, [a] user-friendly system helps people to handle [the] system with necessary options

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

• Akamai API Gateway can reduce risk as well as save money by preventing expensive data breaches, compliance violations, and damage to reputation by improving API security and reducing risks.
• Akamai API Gateway helps increase developer productivity, shorten API development cycles, and allow quicker time-to-market for new products and services with its developer-friendly tools, documentation, and sandbox environments.
• One negative aspect is that advanced security policies or integration setup and configuration can require special knowledge and resources, which can extend the implementation period and price.

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