Amazon API Gateway vs Rest.li: What are the differences?
Developers describe Amazon API Gateway as "Create, publish, maintain, monitor, and secure APIs at any scale". Amazon API Gateway handles all the tasks involved in accepting and processing up to hundreds of thousands of concurrent API calls, including traffic management, authorization and access control, monitoring, and API version management. On the other hand, Rest.li is detailed as "A REST+JSON framework for robust, scalable service architectures, by LinkedIn". Rest.li is an open source REST framework for building robust, scalable RESTful architectures using type-safe bindings and asynchronous, non-blocking IO. Rest.li fills a niche for applying RESTful principals at scale with an end-to-end developer workflow for buildings REST APIs that promotes clean REST practices, uniform interface design and consistent data modeling.
Amazon API Gateway and Rest.li belong to "API Tools" category of the tech stack.
Rest.li is an open source tool with 1.94K GitHub stars and 392 GitHub forks. Here's a link to Rest.li's open source repository on GitHub.
What is Amazon API Gateway?
What is Rest.li?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose Rest.li?
What are the cons of using Amazon API Gateway?
What are the cons of using Rest.li?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Rest.li?
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