We would definitely recommend sticking to native solutions because then you have one Hyperscale provider supporting the applications, storage, compute, and APIs. 

Another aspect to consider is the security features within the API. If you need to collaborate outside the organization, there are numerous security features available through the Hyperscale provider that can be leveraged. 

However, if there is a very specific requirement that the native API Gateway doesn't fulfill, then you can explore other external products or solutions.

Overall, I would rate the solution a nine out of ten.

Overall, I would rate the solution a nine out of ten. There's room for enhancements. Currently, API Gateway lacks some governance features that MuleSoft offers, and there are additional features that could make it even better.

I am an end-user.

I've been using the latest version of the solution. 

I highly recommend the product. 

I'd rate the product ten out of ten. 

Amazon API Gateway serves as a key component that works effectively in our company's serverless architecture. My company uses the product to ensure that we do not expose AWS Lambda to the outside world. In our company, we also use the product's services to protect the API calls.

Request, rate limit, and response validation are some of the most crucial features in API development, deployment, and management. Ease of development and areas involving AWS CodePipeline are also some of the important features attached to Amazon API Gateway.

The API caching feature was very effective in improving our company's API performance. The response has always been good whenever we have used the product's API caching feature in our company. Whenever we need something less sensitive, we prefer to use the tool's API caching feature.

In terms of security features, our company uses API keys and tokens for client credentials flow so that we can authenticate the calls to Amazon API Gateway. There are no concerns about the tool's security features.

The product is easy to maintain. My company hasn't researched the need for multi-region maintenance. When it comes to the multi-region maintenance phase, there could be some complexities involved. In my experience, the maintenance of the product is easy. One person is good enough to maintain the product.

Integrating Amazon API Gateway with other services or products is very easy, especially with the other AWS services or products I use. In general, I find the product's integration capabilities to be easy and straightforward.

If you want to integrate any of the services within AWS and expose your data, Amazon API Gateway is a good way to do it. I definitely recommend others use AWS Serverless Computing and Amazon API Gateway together.

I rate the overall tool a ten out of ten.

Since the deployment should be automatic, it's better to use the Serverless tool to deploy the solution. Otherwise, you can use Terraform. Manually creating something will be a problem. It is easy for somebody to learn to use API Gateway for the first time. When we integrate Amazon API Gateway with any other service like Lambda, there will be a log associated with it, which you can find out.

Overall, I rate the solution an eight out of ten.

If you use AWS services, do not hesitate to go for Amazon API Gateway. If you are not using AWS or if you are not AWS cloud-native, you can consider using other solutions like Apigee or Kong. If you are looking to have a serverless application, then you need to use it again.

Overall, I rate Amazon API Gateway an eight out of ten.

I rate the solution a ten out of ten.

I advise others to use Lambda authorizer instead of API key-based authorization for more secure keys. It will help them use different tokens per customer.

Overall, I would rate the solution an eight out of ten. 

I am involved in the process of integrating Amazon API Gateway with microservices architecture.

I use REST for Amazon API Gateway.

Speaking about how Amazon API Gateway's caching feature has an impact on API performance, I would say that my company has its own caching mechanism written in Java. Even in AWS, our company uses a caching feature.

In terms of the product's authorization and access control features, I would say that there is a component in AWS that we can use. Among the three projects my company handles, for one of the projects, we used LDAP for authorization. In one of the projects handled by our company, we have used AWS as a component.

All the features of the product are good, but it all depends on the end users who need to accept the solution. If you you ask me, the cloud solutions are very good, irrespective of whether users go for AWS, Azure, or GCP.

Considering the monitoring and analytics feature in Amazon API Gateway, I would say that my company used the tool for analytics along with Microsoft, which we recently used for Spring Boot Actuator since it provides production-ready features, including health check metrics. My company also uses a third-party API for analytics purposes.

The monitoring and analytics feature in Amazon API Gateway was the reason I implemented microservices on AWS in some of my earlier projects with a different company. Presently, I work for the Ministry of Interior of Qatar, and we now want to move to microservices. I was involved in doing some research to figure out whether to choose Spring Boot or MicroProfile, an open-source service for microservices.

The product is really good when it comes to API lifecycle management, and it is not just something that includes the balancing part or the security aspect but also the routing and the fallback mechanism.

I recommend the product to those who plan to use it. When you go for a cloud solution, the main advantage is that users can choose not to have an infrastructure, where they may have to opt for a pay-as-you-go model. For small and medium-sized organizations, AWS, Azure, or GCP are fine. In my case, since I have an extensive database, I think it is good to go with Amazon API Gateway.

I rate the solution an eight out of ten.

Amazon is the number one cloud service provider in the world.

I recommend the solution to others since it is a good product.

The benefit that I have experienced from using the solution stems from the fact that it is a secure and reliable product to use.

I rate the overall product a nine out of ten.

Opting for the cloud is a swift decision, and once made, the process proceeds smoothly. The consensus is positive, with no apparent reluctance. However, a crucial point is the necessity for expertise, particularly in AWS. Without the right proficiency, the implementation might not proceed seamlessly. Overall, I would rate it eight out of ten.

The suitability of this solution depends on an organization's use case and architecture.

I would rate this solution an eight out of ten. 

I would recommend the solution to others. You should consider using API Gateway when working with other Amazon cloud components like Amazon RD, Amazon storage, or AWS Lambda for serverless computing. It has its own value separately but API Gateway is interconnected with the broader Amazon service ecosystem. I would overall rate it an eight out of ten. 

Overall, I would rate the solution an eight out of ten. 

I think it's one of the best API management solutions I've used. I've previously worked with other API management tools but prefer the Amazon API Gateway. I rate it a ten out of ten. 

I would recommend API Gateway to those who are uncertain about their API management vision and are already on the AWS platform. It presents an excellent opportunity to start with API management without committing to a specific strategy immediately. Overall, I would rate it six out of ten.

I'd recommend the solution to other users and companies. If you are using AWS components, then it is a good product.

I'd rate the product eight out of ten.

It is the most recommended solution to use.

What I have explored is limited. I am not sure if any other external integrations are required. To my knowledge, they already integrate with other services. We are pleased with what we have.

I would definitely recommend this solution for microservices-based applications. For example, if they are using a Lambda function that is serverless, you will want to move the Lambda functions to the API gateway it is recommended. 

I would rate Amazon API Gateway a nine out of ten.

Speaking about how Amazon API Gateway has facilitated cloud application integration, I use the tool since I want to look at the microservices it offers. I use many of the microservices offered by the product, along with Kubernetes and Lambda.

In terms of securing APIs, I can handle a lot of services on the desktop and also manage the load-balancing part.

My company uses the dashboards provided by the product for API monitoring.

I recommend the product to those who plan to use it.

I recommend the product because it offers many microservices for infrastructures. It can be deployed quickly. The tool can be very expensive. The product is strong when it comes to its autoscaling features and Lambda-related functionalities.

I rate the tool a seven out of ten.

Amazon API Gateway is a solid service. Considering the cost of setting up an API gateway, it’s best to use Amazon API Gateway. Overall, I rate the tool an eight out of ten.

I couldn't recommend the product as it is an on-premise solution, and everyone is shifting the environment to the cloud infrastructure.

I rate it an eight out of ten.

It is very easy for a beginner to learn to use Amazon API Gateway and to create some resources manually. You can download one CDK script to create that same resource in any other environment a second time.

Amazon API Gateway is a serverless product. We don't need to manage servers. We only need to create the resources that we need to create. It is a completely deployed product. We create our AWS account, and we can create APIs directly. We don't need to worry about servers.

Setting up the authorization and authentication mechanism with Amazon API Gateway is very easy and takes only half an hour. We are actively migrating from on-premises to AWS or any other cloud. We will have a very big use case for Amazon API Gateway in the future.

You should be very specific with the configuration if you are a new user. Initially, you should have a very simple configuration and not use a proxy. If you have a use case to expose the Amazon API gateway to any front-end resources, you have to allow CORS and set headers. Be specific with the headers and CORS configuration, and don't make it complex. Don't jump directly into advanced configuration.

Overall, I rate the solution a nine out of ten.

The advice that I would give others regarding Amazon API is that it depends on the use cases. If they have a complex environment, they need to consider different integration patterns. It could be that AWS Management is not enough for them. They would have to compliment it with another solution. It is really working in some cases, but you do need to evaluate all the requirements to choose the tool. If you are working only in the AWS context with different services or something like that, it's really useful to work with AWS Management.

On a scale of one to ten I would rate Amazon API Gateway an eight.

It is doing what we need at this point, there isn't anything extra that we would want.

I would recommend this solution to others who are interested in using it.

I would rate Amazon API Gateway a seven out of ten.

My advice to anybody who is implementing this solution is to first read the documentation and follow the steps. Make a use case, create a proof of concept, and then migrate it to production environments. It's pretty easy to use.

This is a good product, but there is always room for improvement.

I would rate this solution an eight out of ten.

Overall, the solution is a nine out of ten. 

My company has around three to four team members who use Amazon API Gateway, but the solution is also being used by many clients who connect to it and consume APIs.

Amazon API Gateway is being used daily.

I advise anyone looking into using Amazon API Gateway to go ahead and use the solution. Still, you should consider your load requirements and what you're looking for in a solution before making that decision.

My rating for Amazon API Gateway is nine out of ten.

I'm a customer of Amazon API Gateway.

This is a good solution for anyone whose strategy is to run entirely on Amazon. You basically have to use another approach if that's not the case. If you have a hybrid cloud or if you are trying to be independent of the cloud, this is not a good solution for you. 

I would rate Amazon API Gateway an eight out of ten. It is a complete solution.

I rate the solution a nine out of ten.

The user interface is easy enough to use. I don't really have any complaints about it. In terms of advice for implementing and using, I would say you should make sure you've got good internal skills.

I would rate this solution 8 out of 10.

I would rate this solution 8 out of 10.

If you get used to a certain technology, you would definitely recommend it to your customer because you have experience. We recommend this technology to our customers because we are using it for other products and we have experience, and then the core learning or integration course is shorter.

My advice to others would be for them to keep their eye on the cost.

I rate Amazon API Gateway a nine out of ten.

I recommend it for open banking. I would rate it 8 out of 10. To get to 10 it would It would need more support for open banking, via the open API. If your existing workloads are in AWS, then you can surely go for the AWS Amazon, AWS API gateway. If it is a hybrid solution, then I would suggest you go for WSA2. Konghybrid GCP is also good.

I would rate Amazon API Gateway a nine out of ten.

I would rate this solution a five out of 10. If there was a better configuration, I'd give it a higher score.

I have heard complaints that people say this product does not have good security, but that is not true. There is an expectation that you can use it with other Amazon services to provide security, as well as other functionality.

This is a great product. It has ease of use and a full breadth of functionality. I would say that the Amazon platform, in my view, is the best compared to third-party products.

The only real problem is that you have to know a lot about what is outside of the API gateway in order to make the best use of it.

I would rate this solution an eight out of ten.