Alternatives to Apigee logo

Alternatives to Apigee

Mashery, Zuul, Kong, WSO2, and Istio are the most popular alternatives and competitors to Apigee.
166
454
+ 1
25

What is Apigee and what are its top alternatives?

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

Top Alternatives to Apigee

  • Mashery

    Mashery

    Sign In and discover new APIs from our open data commons of RESTful APIs. Mashery's API management offerings include strategic consulting & developer support to help you build your business. ...

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

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

  • WSO2

    WSO2

    It delivers the only complete open source middleware platform. With its revolutionary componentized design, it is also the only open source platform-as-a-service for private and public clouds available today. With it, seamless migration and integration between servers, private clouds, and public clouds is now a reality. ...

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

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

Apigee alternatives & related posts

Mashery logo

Mashery

12
19
2
Manage your API and discover new APIs
12
19
+ 1
2
PROS OF MASHERY
  • 1
    Hard to use
  • 1
    Cheese-like
CONS OF MASHERY
    Be the first to leave a con

    related Mashery posts

    Zuul logo

    Zuul

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

      related Zuul posts

      Kong logo

      Kong

      393
      953
      124
      Open Source Microservice & API Management Layer
      393
      953
      + 1
      124
      PROS OF KONG
      • 36
        Easy to maintain
      • 30
        Easy to install
      • 22
        Flexible
      • 20
        Great performance
      • 5
        Api blueprint
      • 4
        Custom Plugins
      • 3
        Kubernetes-native
      • 2
        Agnostic
      • 1
        Documentation is clear
      • 1
        1
      • 0
        12
      • 0
        123123
      • 0
        123
      • 0
        12312312
      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
        KongKongIstioIstio

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

        See more
        WSO2 logo

        WSO2

        50
        95
        0
        A comprehensive middleware platform that is open source with no gimmicks
        50
        95
        + 1
        0
        PROS OF WSO2
          Be the first to leave a pro
          CONS OF WSO2
            Be the first to leave a con

            related WSO2 posts

            Istio logo

            Istio

            549
            968
            41
            Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
            549
            968
            + 1
            41
            PROS OF ISTIO
            • 10
              Zero code for logging and monitoring
            • 8
              Service Mesh
            • 7
              Great flexibility
            • 4
              Ingress controller
            • 3
              Easy integration with Kubernetes and Docker
            • 3
              Powerful authorization mechanisms
            • 3
              Resiliency
            • 3
              Full Security
            CONS OF ISTIO
            • 8
              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
            Postman logo

            Postman

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

            related Postman posts

            Noah Zoschke
            Engineering Manager at Segment · | 30 upvotes · 1.8M 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.5M 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

            1K
            748
            37
            Create, publish, maintain, monitor, and secure APIs at any scale
            1K
            748
            + 1
            37
            PROS OF AMAZON API GATEWAY
            • 35
              AWS Integration
            • 2
              Websockets
            CONS OF AMAZON API GATEWAY
            • 1
              No websocket broadcast
            • 1
              Less expensive

            related Amazon API Gateway posts

            A Luthra
            VP Software Engrg at Reliant · | 2 upvotes · 174K 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
            Insomnia REST Client logo

            Insomnia REST Client

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

            related Insomnia REST Client posts

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