Alternatives to Amazon API Gateway logo

Alternatives to Amazon API Gateway

Apigee, Kong, NGINX, Zuul, and Azure API Management are the most popular alternatives and competitors to Amazon API Gateway.
1.1K
835
+ 1
41

What is Amazon API Gateway and what are its top alternatives?

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.
Amazon API Gateway is a tool in the API Tools category of a tech stack.

Top Alternatives to Amazon API Gateway

  • Apigee

    Apigee

    API management, design, analytics, and security are at the heart of modern digital architecture. The Apigee intelligent API platform is a complete solution for moving business to the digital world. ...

  • Kong

    Kong

    Kong is a scalable, open source API Layer (also known as an API Gateway, or API Middleware). Kong controls layer 4 and 7 traffic and is extended through Plugins, which provide extra functionality and services beyond the core platform. ...

  • NGINX

    NGINX

    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018. ...

  • Zuul

    Zuul

    It is the front door for all requests from devices and websites to the backend of the Netflix streaming application. As an edge service application, It is built to enable dynamic routing, monitoring, resiliency, and security. Routing is an integral part of a microservice architecture. ...

  • Azure API Management

    Azure API Management

    Today's innovative enterprises are adopting API architectures to accelerate growth. Streamline your work across hybrid and multi-cloud environments with a single place for managing all your APIs. ...

  • Postman

    Postman

    It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide. ...

  • Insomnia REST Client

    Insomnia REST Client

    Insomnia is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux. ...

  • OpenAPI

    OpenAPI

    It is a publicly available application programming interface that provides developers with programmatic access to a proprietary software application or web service. ...

Amazon API Gateway alternatives & related posts

Apigee logo

Apigee

182
512
26
Intelligent and complete API platform
182
512
+ 1
26
PROS OF APIGEE
  • 10
    Highly scalable and secure API Management Platform
  • 5
    Quick jumpstart
  • 5
    Good documentation
  • 3
    Fast and adjustable caching
  • 3
    Easy to use
CONS OF APIGEE
  • 8
    Expensive

related Apigee posts

A Luthra
VP Software Engrg at Reliant · | 3 upvotes · 410.7K views
Shared insights
on
Apigee
Amazon API Gateway

Amazon API Gateway vs Apigee. How do they compare as an API Gateway? What is the equivalent functionality, similarities, and differences moving from Apigee API GW to AWS API GW?

See more
Kong logo

Kong

464
1.1K
130
Open Source Microservice & API Management Layer
464
1.1K
+ 1
130
PROS OF KONG
  • 36
    Easy to maintain
  • 30
    Easy to install
  • 24
    Flexible
  • 20
    Great performance
  • 5
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Agnostic
  • 1
    Documentation is clear
  • 1
    1
  • 1
    123123
  • 1
    12312312
  • 1
    123
  • 1
    12
CONS OF KONG
    Be the first to leave a con

    related Kong posts

    Al Tsang
    Problem/Challenge

    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

    See more
    Anas MOKDAD
    Shared insights
    on
    Kong
    Istio

    As for the new support of service mesh pattern by Kong, I wonder how does it compare to Istio?

    See more
    NGINX logo

    NGINX

    92.7K
    43.1K
    5.5K
    A high performance free open source web server powering busiest sites on the Internet.
    92.7K
    43.1K
    + 1
    5.5K
    PROS OF NGINX
    • 1.4K
      High-performance http server
    • 896
      Performance
    • 728
      Easy to configure
    • 606
      Open source
    • 529
      Load balancer
    • 286
      Scalability
    • 285
      Free
    • 222
      Web server
    • 173
      Simplicity
    • 134
      Easy setup
    • 29
      Content caching
    • 19
      Web Accelerator
    • 14
      Capability
    • 13
      Fast
    • 11
      Predictability
    • 10
      High-latency
    • 7
      Reverse Proxy
    • 6
      Supports http/2
    • 6
      Fast and lightweight
    • 4
      Enterprise version
    • 4
      Great Community
    • 4
      The best of them
    • 4
      Lots of Modules
    • 3
      Streaming media
    • 3
      Embedded Lua scripting
    • 3
      Reversy Proxy
    • 3
      Streaming media delivery
    • 3
      High perfomance proxy server
    • 2
      Lightweight
    • 2
      Slim
    • 2
      saltstack
    • 2
      Fast and easy to set up
    • 1
      Blash
    • 1
      GRPC-Web
    • 1
      Ingress controller
    • 1
      Virtual hosting
    • 1
      Narrow focus. Easy to configure. Fast
    • 1
      Along with Redis Cache its the Most superior
    • 0
      A
    CONS OF NGINX
    • 8
      Advanced features require subscription

    related NGINX posts

    Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

    We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

    See more
    Gabriel Pa
    Shared insights
    on
    Traefik
    NGINX
    at

    We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

    We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

    The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

    See more
    Zuul logo

    Zuul

    152
    288
    6
    An edge service that provides dynamic routing, monitoring, resiliency, security, and more
    152
    288
    + 1
    6
    PROS OF ZUUL
    • 6
      Load blancing
    CONS OF ZUUL
      Be the first to leave a con

      related Zuul posts

      Azure API Management logo

      Azure API Management

      30
      44
      0
      Hybrid, multi-cloud management platform for APIs across all environments
      30
      44
      + 1
      0
      PROS OF AZURE API MANAGEMENT
        Be the first to leave a pro
        CONS OF AZURE API MANAGEMENT
          Be the first to leave a con

          related Azure API Management posts

          Postman logo

          Postman

          62.2K
          50.3K
          1.8K
          Only complete API development environment
          62.2K
          50.3K
          + 1
          1.8K
          PROS OF POSTMAN
          • 486
            Easy to use
          • 369
            Great tool
          • 275
            Makes developing rest api's easy peasy
          • 156
            Easy setup, looks good
          • 143
            The best api workflow out there
          • 53
            It's the best
          • 53
            History feature
          • 44
            Adds real value to my workflow
          • 42
            Great interface that magically predicts your needs
          • 34
            The best in class app
          • 11
            Can save and share script
          • 9
            Fully featured without looking cluttered
          • 7
            Collections
          • 7
            Global/Environment Variables
          • 7
            Option to run scrips
          • 6
            Shareable Collections
          • 6
            Dead simple and useful. Excellent
          • 6
            Dark theme easy on the eyes
          • 5
            Awesome customer support
          • 5
            Great integration with newman
          • 4
            The test script is useful
          • 3
            Makes testing API's as easy as 1,2,3
          • 3
            Easy as pie
          • 3
            Saves responses
          • 3
            This has simplified my testing significantly
          • 3
            Simple
          • 3
            Documentation
          • 2
            Mocking API calls with predefined response
          • 2
            I'd recommend it to everyone who works with apis
          • 2
            API-network
          • 1
            Easy to setup, test and provides test storage
          • 1
            Continuous integration using newman
          • 1
            Graph
          • 1
            Pre-request Script and Test attributes are invaluable
          • 1
            Postman Runner CI Integration
          • 1
            Now supports GraphQL
          • 0
            <a href="http://fixbit.com/">useful tool</a>
          • 0
            Runner
          CONS OF POSTMAN
          • 9
            Stores credentials in HTTP
          • 7
            Poor GraphQL support
          • 7
            Bloated features and UI
          • 6
            Cumbersome to switch authentication tokens
          • 2
            Expensive
          • 1
            Support websocket
          • 1
            Import curl
          • 1
            Import swagger
          • 1
            Can't prompt for per-request variables

          related Postman posts

          Noah Zoschke
          Engineering Manager at Segment · | 30 upvotes · 2M views

          We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

          Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

          Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

          This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

          Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

          Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

          Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

          See more
          Simon Reymann
          Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2M views

          Our whole Node.js backend stack consists of the following tools:

          • Lerna as a tool for multi package and multi repository management
          • npm as package manager
          • NestJS as Node.js framework
          • TypeScript as programming language
          • ExpressJS as web server
          • Swagger UI for visualizing and interacting with the API’s resources
          • Postman as a tool for API development
          • TypeORM as object relational mapping layer
          • JSON Web Token for access token management

          The main reason we have chosen Node.js over PHP is related to the following artifacts:

          • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
          • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
          • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
          • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
          See more
          Insomnia REST Client logo

          Insomnia REST Client

          557
          462
          37
          The most intuitive cross-platform REST API Client 😴
          557
          462
          + 1
          37
          PROS OF INSOMNIA REST CLIENT
          • 15
            Easy to work with
          • 10
            Great user interface
          • 6
            Works with GraphQL
          • 2
            Cross platform, available for Mac, Windows, and Linux
          • 2
            Opensource
          • 2
            Preserves request templates
          • 0
            Vim and Emacs key map
          • 0
            Does not have history feature
          CONS OF INSOMNIA REST CLIENT
          • 2
            Do not store credentials in HTTP
          • 2
            Do not have team sharing options

          related Insomnia REST Client posts

          Jason Barry
          Cofounder at FeaturePeek · | 4 upvotes · 1.9M views

          We've tried a couple REST clients over the years, and Insomnia REST Client has won us over the most. Here's what we like about it compared to other contenders in this category:

          • Uncluttered UI. Things are only in your face when you need them, and the app is visually organized in an intuitive manner.
          • Native Mac app. We wanted the look and feel to be on par with other apps in our OS rather than a web app / Electron app (cough Postman).
          • Easy team sync. Other apps have this too, but Insomnia's model best sets the "set and forget" mentality. Syncs are near instant and I'm always assured that I'm working on the latest version of API endpoints. Apps like Paw use a git-based approach to revision history, but I think this actually over-complicates the sync feature. For ensuring I'm always working on the latest version of something, I'd rather have the sync model be closer to Dropbox's than git's, and Insomnia is closer to Dropbox in that regard.

          Some features like automatic public-facing documentation aren't supported, but we currently don't have any public APIs, so this didn't matter to us.

          See more
          OpenAPI logo

          OpenAPI

          307
          254
          0
          Allows the owner of a network-accessible service to give universal access
          307
          254
          + 1
          0
          PROS OF OPENAPI
            Be the first to leave a pro
            CONS OF OPENAPI
              Be the first to leave a con

              related OpenAPI posts

              Joshua Dean Küpper
              CEO at Scrayos UG (haftungsbeschränkt) · | 4 upvotes · 216.6K views

              We use Swagger Inspector in conjunction with our universal REST-API "Charon". Swagger Inspector makes testing edge-cases hassle-free and lets testing look easy. Swagger Inspector was also a great help to explore the Mojang-API, that we are dependent on, because it is the central repository for minecraft-account-data.

              We previously used Postman but decided to switch over to Swagger Inspector because it also integrated seamlessly into Swagger UI, which we use for displaying our OpenAPI specification of said REST-API.

              See more