Amazon API Gateway vs Falcor: What are the differences?
Amazon API Gateway and Falcor can be primarily classified as "API" tools.
Some of the features offered by Amazon API Gateway are:
- Build, Deploy and Manage APIs
- API Lifecycle Management
On the other hand, Falcor provides the following key features:
- One Model Everywhere
- The Data is the API
- Bind to the Cloud
Falcor is an open source tool with 9.34K GitHub stars and 448 GitHub forks. Here's a link to Falcor's open source repository on GitHub.
Intuit, Repro, and Simple Merchant are some of the popular companies that use Amazon API Gateway, whereas Falcor is used by Netflix, AngularClass, and PiggyPot. Amazon API Gateway has a broader approval, being mentioned in 167 company stacks & 62 developers stacks; compared to Falcor, which is listed in 5 company stacks and 4 developer stacks.
What is Amazon API Gateway?
What is Falcor?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
What are the cons of using Amazon API Gateway?
What are the cons of using Falcor?
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
API Gateway in conjunction with Lambda has allowed us to become 'serverless'. We have a number of API endpoints that range from simple CRUD operations, through to triggering chains of complex background jobs. Like Lambda, this service has released us from getting bogged down in infrastructure management, freeing up huge amounts of time to focus on solving business problems.
It provides me with POST endpoints; I don't run servers and some third-party services need to POST data to my application.
Triggers the Lambda function from a GitHub WebHook push into
Excellent API Gateway, some quirks but most are being addressed over time, easy integration with Lambda