Alternatives to Express Gateway logo

Alternatives to Express Gateway

Kong, Apigee, LoopBack, NGINX, and Zuul are the most popular alternatives and competitors to Express Gateway.
59
156
+ 1
12

What is Express Gateway and what are its top alternatives?

A cloud-native microservices gateway completely configurable and extensible through JavaScript/Node.js built for ALL platforms and languages. Enterprise features are FREE thanks to the power of 3K+ ExpressJS battle hardened modules.
Express Gateway is a tool in the Microservices Tools category of a tech stack.

Top Alternatives to Express Gateway

  • 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. ...

  • 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. ...

  • LoopBack
    LoopBack

    A highly-extensible, open-source Node.js framework that enables you to create dynamic end-to-end REST APIs with little or no coding. Connect to multiple data sources, write business logic in Node.js, glue on top of your existing services and data, connect using JS, iOS & Android SDKs. ...

  • 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. ...

  • Istio
    Istio

    Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes, Mesos, etc. ...

  • linkerd
    linkerd

    linkerd is an out-of-process network stack for microservices. It functions as a transparent RPC proxy, handling everything needed to make inter-service RPC safe and sane--including load-balancing, service discovery, instrumentation, and routing. ...

  • Jersey
    Jersey

    It is open source, production quality, framework for developing RESTful Web Services in Java that provides support for JAX-RS APIs and serves as a JAX-RS (JSR 311 & JSR 339) Reference Implementation. It provides it’s own API that extend the JAX-RS toolkit with additional features and utilities to further simplify RESTful service and client development. ...

Express Gateway alternatives & related posts

Kong logo

Kong

513
1.3K
128
Open Source Microservice & API Management Layer
513
1.3K
+ 1
128
PROS OF KONG
  • 36
    Easy to maintain
  • 31
    Easy to install
  • 24
    Flexible
  • 20
    Great performance
  • 5
    Api blueprint
  • 4
    Custom Plugins
  • 3
    Kubernetes-native
  • 2
    Agnostic
  • 1
    Security
  • 1
    Documentation is clear
  • 1
    Load balancing
CONS OF KONG
    Be the first to leave a con

    related Kong posts

    Anas MOKDAD
    Shared insights
    on
    KongKongIstioIstio

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

    See more
    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
    Apigee logo

    Apigee

    199
    600
    29
    Intelligent and complete API platform
    199
    600
    + 1
    29
    PROS OF APIGEE
    • 12
      Highly scalable and secure API Management Platform
    • 6
      Quick jumpstart
    • 5
      Good documentation
    • 3
      Fast and adjustable caching
    • 3
      Easy to use
    CONS OF APIGEE
    • 9
      Expensive

    related Apigee posts

    A Luthra
    VP Software Engrg at Reliant · | 3 upvotes · 593K views
    Shared insights
    on
    ApigeeApigeeAmazon API GatewayAmazon 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
    LoopBack logo

    LoopBack

    268
    522
    31
    Build modern API applications that require complex integrations
    268
    522
    + 1
    31
    PROS OF LOOPBACK
    • 10
      Need a nodejs ReST-API, DB, AAA, Swagger? Then loopback
    • 9
      Easy Database Migration
    • 5
      Code generator
    • 4
      The future of API's
    • 2
      GraphQL
    • 1
      Typescript
    CONS OF LOOPBACK
    • 7
      Community is slow
    • 1
      Backward compatibility

    related LoopBack posts

    Samuel Olugbemi
    Software Engineer at Payzone UK · | 6 upvotes · 141.7K views
    Shared insights
    on
    LoopBackLoopBackExpressJSExpressJS
    at

    I use LoopBack because it is: * It is truly and Unbelievably Extensible * it is default integrated with OpenAPI (Swagger) Spec Driven REST API * I write lesser codes, because most of the user stories have been covered using the code generation * It's documentation is more compact and well detailed than ExpressJS * It is very easy to learn, hence you can build a basic Rest API App in minutes * It has built in NPM packages required to build my Rest API which saves me time on installation and configuration * The Datasource/Service/Controller concept is just Brilliant (that's mostly all you need to get your app speaking with an External API services) * The support for SOAP and Rest API services is amazing!

    See more
    Shared insights
    on
    NestJSNestJSJestJestLoopBackLoopBack

    We inherited this project and the backend is using LoopBack v3. I haven't taken a look at Loopback.io v4, but I'm planning to replace it. The reason being is that Loopback v3 documentation is a bit confusing and we are having trouble packaging the build using Webpack. Not to mention, integrating unit tests (latest Jest).

    I still think Loopback is a great tool, but their documentation is really "messy" and hard to navigate through. There's also a constraint of time from our side. So what's the best option out there?

    Should I try upgrading to Loopback v4, or trying other stuff? (i.e. NestJS)

    Thanks!

    See more
    NGINX logo

    NGINX

    100.4K
    50.1K
    5.5K
    A high performance free open source web server powering busiest sites on the Internet.
    100.4K
    50.1K
    + 1
    5.5K
    PROS OF NGINX
    • 1.4K
      High-performance http server
    • 893
      Performance
    • 727
      Easy to configure
    • 606
      Open source
    • 529
      Load balancer
    • 287
      Scalability
    • 286
      Free
    • 223
      Web server
    • 174
      Simplicity
    • 135
      Easy setup
    • 29
      Content caching
    • 20
      Web Accelerator
    • 14
      Capability
    • 13
      Fast
    • 11
      High-latency
    • 11
      Predictability
    • 7
      Reverse Proxy
    • 6
      Supports http/2
    • 5
      The best of them
    • 4
      Great Community
    • 4
      Lots of Modules
    • 4
      Enterprise version
    • 3
      High perfomance proxy server
    • 3
      Embedded Lua scripting
    • 3
      Reversy Proxy
    • 3
      Streaming media delivery
    • 3
      Streaming media
    • 2
      Fast and easy to set up
    • 2
      Slim
    • 2
      Blash
    • 2
      Lightweight
    • 2
      saltstack
    • 1
      Virtual hosting
    • 1
      Along with Redis Cache its the Most superior
    • 1
      Ingress controller
    • 1
      Narrow focus. Easy to configure. Fast
    • 1
      GRPC-Web
    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
    TraefikTraefikNGINXNGINX
    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

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

      related Zuul posts

      Istio logo

      Istio

      704
      1.3K
      45
      Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
      704
      1.3K
      + 1
      45
      PROS OF ISTIO
      • 13
        Zero code for logging and monitoring
      • 8
        Service Mesh
      • 7
        Great flexibility
      • 4
        Powerful authorization mechanisms
      • 4
        Ingress controller
      • 3
        Full Security
      • 3
        Resiliency
      • 3
        Easy integration with Kubernetes and Docker
      CONS OF ISTIO
      • 15
        Performance

      related Istio posts

      Anas MOKDAD
      Shared insights
      on
      KongKongIstioIstio

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

      See more
      linkerd logo

      linkerd

      112
      270
      7
      Twitter-Style Operability for Microservices
      112
      270
      + 1
      7
      PROS OF LINKERD
      • 3
        CNCF Project
      • 1
        Fast Integration
      • 1
        Pre-check permissions
      • 1
        Light Weight
      • 1
        Service Mesh
      CONS OF LINKERD
        Be the first to leave a con

        related linkerd posts

        Jersey logo

        Jersey

        101
        107
        5
        A REST framework that provides a JAX-RS implementation
        101
        107
        + 1
        5
        PROS OF JERSEY
        • 3
          Lightweight
        • 1
          Fast Performance With Microservices
        • 1
          Java standard
        CONS OF JERSEY
          Be the first to leave a con

          related Jersey posts