Apigee vs Express Gateway: What are the differences?
Apigee can be classified as a tool in the "API Tools" category, while Express Gateway is grouped under "Microservices Tools".
Some of the features offered by Apigee are:
- Design, secure, analyze, and scale your APIs with the Apigee Edge API management platform.
- Predictive analytics to ensure intelligent and customized interactions.
- Connect devices to the Internet, and enable partners and developers to access device functionality and data with APIs.
On the other hand, Express Gateway provides the following key features:
- API Management
"Highly scalable and secure API Management Platform" is the top reason why over 5 developers like Apigee, while over 3 developers mention "Microservices, Body manipulation" as the leading cause for choosing Express Gateway.
According to the StackShare community, Apigee has a broader approval, being mentioned in 5 company stacks & 11 developers stacks; compared to Express Gateway, which is listed in 11 company stacks and 3 developer stacks.
What is Apigee?
What is Express Gateway?
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 Express Gateway?
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
We needed a lightweight and completely customizable #microservices #gateway to be able to generate #JWT and introspect #OAuth2 tokens as well. The #gateway was going to front all #APIs for our single page web app as well as externalized #APIs for our partners.Contenders
We looked at Tyk Cloud and Kong. Kong's plugins are all Lua based and its core is NGINX and OpenResty. Although it's open source, it's not the greatest platform to be able to customize. On top of that enterprise features are paid and expensive. Tyk is Go and the nomenclature used within Tyk like "sessions" was bizarre, and again enterprise features were paid.Decision
We ultimately decided to roll our own using ExpressJS into Express Gateway because the use case for using ExpressJS as an #API #gateway was tried and true, in fact - all the enterprise features that the other two charge for #OAuth2 introspection etc were freely available within ExpressJS middleware.Outcome
We opened source Express Gateway with a core set of plugins and the community started writing their own and could quickly do so by rolling lots of ExpressJS middleware into Express Gateway