AWS offers the Amazon API Gateway supports the creation and publication of an API for web applications, as well as its monitoring and maintenance. The Amazon API Gateway is able to support thousands of API calls concurrently and provides traffic management, as well as monitoring and access control.
$0.90
Per Million
Blackbird API Development
Score 10.0 out of 10
N/A
Ambassador offers a suite of products designed to deliver API developer experiences that fuel innovation. Blackbird API Development Platform enables developers to spec, mock, write boilerplate code, and debug APIs faster.
$10
per month (for a single user and 5 concurrent instances)
Pricing
Amazon API Gateway
Blackbird API Development
Editions & Modules
Past 300 Million
$0.90
Per Million
First 300 Million
$1.00
Per Million
No answers on this topic
Offerings
Pricing Offerings
Amazon API Gateway
Blackbird API Development
Free Trial
No
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Amazon API Gateway
Blackbird API Development
Features
Amazon API Gateway
Blackbird API Development
API Management
Comparison of API Management features of Product A and Product B
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.
Ambassador is really well suited for scenarios were you need to give power and freedom to your developers so they can take advantage of the self-service approach. One of the few scenarios I can not recommend using Ambassador is in the case you are planning to not using Kubernetes as it is a solution designed to work specifically on that platform
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.
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
It's great! it's amazingly simple to use and the best part is the self-service approach. I also like how easy it is to add a new route to a endpoint with the mappings definition.
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.
Overall the support has been great and quick to answer the requests I've submitted in the past. I was originally using the community/open source version and I can't say it was the best experience I had, it wasn't terrible but it wasn't great. I believe the biggest issue was that they refer to the documentation a lot but the documentation isn't updated regularly so I feel it's lagging behind the most recent versions.
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.
They both offer about the same in terms of end goal and purpose of use and scenarios. However, Ambassador does way better in terms of simplifying the syntax and makes offer a little bit more of control by adding the concepts of hosts, mappings while staying away from a hard to read single file configuration.
