Alternatives to API Umbrella logo

Alternatives to API Umbrella

Kong, Gravitee.io, Postman, Amazon API Gateway, and Insomnia REST Client are the most popular alternatives and competitors to API Umbrella.
22
86
+ 1
0

What is API Umbrella and what are its top alternatives?

API Umbrella is a proxy that sits in front of your APIs. It can seamlessly add common functionality like api keys, rate limiting, and analytics to any API.
API Umbrella is a tool in the API Tools category of a tech stack.
API Umbrella is an open source tool with 1.6K GitHub stars and 290 GitHub forks. Here’s a link to API Umbrella's open source repository on GitHub

Top Alternatives to API Umbrella

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

  • Gravitee.io

    Gravitee.io

    It is a flexible, lightweight and blazing-fast open source API Platform that helps your organization control finely who, when and how users access 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. ...

  • Amazon API Gateway

    Amazon API Gateway

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

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

  • Paw

    Paw

    Paw is a full-featured and beautifully designed Mac app that makes interaction with REST services delightful. Either you are an API maker or consumer, Paw helps you build HTTP requests, inspect the server's response and even generate client code. ...

  • OpenAPI Specification

    OpenAPI Specification

    It defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection. ...

API Umbrella alternatives & related posts

Kong logo

Kong

365
845
121
Open Source Microservice & API Management Layer
365
845
+ 1
121

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
Gravitee.io logo

Gravitee.io

14
58
1
Open source API Platform
14
58
+ 1
1

related Gravitee.io posts

related Postman posts

Noah Zoschke
Engineering Manager at Segment ¡ | 30 upvotes ¡ 1.7M 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 ¡ | 23 upvotes ¡ 1.3M 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
Amazon API Gateway logo

Amazon API Gateway

945
689
37
Create, publish, maintain, monitor, and secure APIs at any scale
945
689
+ 1
37

related Amazon API Gateway posts

A Luthra
VP Software Engrg at Reliant ¡ | 2 upvotes ¡ 68.8K 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

related Insomnia REST Client posts

Jason Barry
Cofounder at FeaturePeek ¡ | 4 upvotes ¡ 1.6M 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

201
152
0
Allows the owner of a network-accessible service to give universal access
201
152
+ 1
0
PROS OF OPENAPI
    No pros available
    CONS OF OPENAPI
      No cons available

      related OpenAPI posts

      Joshua Dean KĂźpper
      CEO at Scrayos UG (haftungsbeschränkt) ¡ | 4 upvotes ¡ 131.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

      related Paw posts

      Jason Barry
      Cofounder at FeaturePeek ¡ | 4 upvotes ¡ 1.6M 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 Specification logo

      OpenAPI Specification

      151
      79
      6
      An API description format for REST APIs
      151
      79
      + 1
      6
      PROS OF OPENAPI SPECIFICATION
      CONS OF OPENAPI SPECIFICATION
        No cons available

        related OpenAPI Specification posts