Alternatives to OpenAPI logo

Alternatives to OpenAPI

JsonAPI, Postman, GraphQL, OData, and RAML are the most popular alternatives and competitors to OpenAPI.
256
226
+ 1
0

What is OpenAPI and what are its top alternatives?

It is a publicly available application programming interface that provides developers with programmatic access to a proprietary software application or web service.
OpenAPI is a tool in the API Tools category of a tech stack.
OpenAPI is an open source tool with 19.5K GitHub stars and 7K GitHub forks. Here’s a link to OpenAPI's open source repository on GitHub

Top Alternatives to OpenAPI

  • JsonAPI

    JsonAPI

    t is a format that works with HTTP. A main goal of the specification is to optimize HTTP requests both in terms of the number of requests and the size of data packages exchanged between clients and servers. ...

  • Postman

    Postman

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

  • GraphQL

    GraphQL

    GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012. ...

  • OData

    OData

    It is an ISO/IEC approved, OASIS standard that defines a set of best practices for building and consuming RESTful APIs. It helps you focus on your business logic while building RESTful APIs without having to worry about the various approaches to define request and response headers, status codes, HTTP methods, URL conventions, media types, payload formats, query options, etc. ...

  • RAML

    RAML

    RESTful API Modeling Language (RAML) makes it easy to manage the whole API lifecycle from design to sharing. It's concise - you only write what you need to define - and reusable. It is machine readable API design that is actually human friendly. ...

  • gRPC

    gRPC

    gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking... ...

  • REST

    REST

    An architectural style for developing web services. A distributed system framework that uses Web protocols and technologies. ...

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

OpenAPI alternatives & related posts

JsonAPI logo

JsonAPI

76
76
0
A specification for building apis in json
76
76
+ 1
0
PROS OF JSONAPI
    Be the first to leave a pro
    CONS OF JSONAPI
      Be the first to leave a con

      related JsonAPI posts

      Postman logo

      Postman

      56.2K
      44.6K
      1.7K
      Only complete API development environment
      56.2K
      44.6K
      + 1
      1.7K
      PROS OF POSTMAN
      • 481
        Easy to use
      • 366
        Great tool
      • 274
        Makes developing rest api's easy peasy
      • 154
        Easy setup, looks good
      • 142
        The best api workflow out there
      • 53
        History feature
      • 53
        It's the best
      • 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
        Awesome customer support
      • 5
        Great integration with newman
      • 4
        The test script is useful
      • 3
        This has simplified my testing significantly
      • 3
        Easy as pie
      • 3
        Simple
      • 3
        Documentation
      • 3
        Makes testing API's as easy as 1,2,3
      • 3
        Saves responses
      • 2
        API-network
      • 2
        Mocking API calls with predefined response
      • 2
        I'd recommend it to everyone who works with apis
      • 1
        Pre-request Script and Test attributes are invaluable
      • 1
        Postman Runner CI Integration
      • 1
        Now supports GraphQL
      • 1
        Continuous integration using newman
      • 1
        Easy to setup, test and provides test storage
      • 1
        Graph
      • 0
        <a href="http://fixbit.com/">useful tool</a>
      • 0
        Runner
      CONS OF POSTMAN
      • 8
        Stores credentials in HTTP
      • 7
        Poor GraphQL support
      • 6
        Bloated features and UI
      • 5
        Cumbersome to switch authentication tokens
      • 1
        Expensive
      • 1
        Can't prompt for per-request variables

      related Postman posts

      Noah Zoschke
      Engineering Manager at Segment · | 30 upvotes · 1.9M 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 · | 24 upvotes · 1.7M 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
      GraphQL logo

      GraphQL

      19.3K
      15.5K
      291
      A data query language and runtime
      19.3K
      15.5K
      + 1
      291
      PROS OF GRAPHQL
      • 69
        Schemas defined by the requests made by the user
      • 62
        Will replace RESTful interfaces
      • 59
        The future of API's
      • 47
        The future of databases
      • 12
        Self-documenting
      • 11
        Get many resources in a single request
      • 5
        Ask for what you need, get exactly that
      • 4
        Query Language
      • 3
        Evolve your API without versions
      • 3
        Type system
      • 2
        GraphiQL
      • 2
        Ease of client creation
      • 2
        Fetch different resources in one request
      • 2
        Easy setup
      • 1
        Good for apps that query at build time. (SSR/Gatsby)
      • 1
        Backed by Facebook
      • 1
        Easy to learn
      • 1
        "Open" document
      • 1
        Better versioning
      • 1
        Standard
      • 1
        1. Describe your data
      • 1
        Fast prototyping
      CONS OF GRAPHQL
      • 3
        Hard to migrate from GraphQL to another technology
      • 3
        More code to type.
      • 1
        Works just like any other API at runtime
      • 1
        Takes longer to build compared to schemaless.

      related GraphQL posts

      Shared insights
      on
      Node.js
      GraphQL
      MongoDB

      I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery

      For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:

      1. Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have

      2. GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.

      3. MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website

      See more
      Nick Rockwell
      SVP, Engineering at Fastly · | 42 upvotes · 1.6M views

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more
      OData logo

      OData

      32
      87
      32
      A REST-based protocol for querying and updating data
      32
      87
      + 1
      32
      PROS OF ODATA
      • 6
        Patterns for paging, sorting, filtering
      • 4
        ISO Standard
      • 3
        Query Language
      • 3
        No overfetching, no underfetching
      • 3
        RESTful
      • 2
        Get many resources in a single request
      • 2
        Ask for what you need, get exactly that
      • 2
        Self-documenting
      • 2
        Batch requests
      • 2
        Bulk requests ("array upsert")
      • 1
        Resource model defines conventional operations
      • 1
        Evolve your API by following the compatibility rules
      • 1
        Resource Modification Language
      CONS OF ODATA
      • 1
        Overwhelming, no "baby steps" documentation

      related OData posts

      RAML logo

      RAML

      149
      141
      35
      RESTful API Modeling Language (RAML) makes it easy to manage the whole API lifecycle from design to sharing
      149
      141
      + 1
      35
      PROS OF RAML
      • 11
        API Specification
      • 7
        Human Readable
      • 6
        API Documentation
      • 3
        Design Patterns & Code Reuse
      • 2
        API Modeling
      • 2
        Automatic Generation of Mule flow
      • 2
        Unit Testing
      • 1
        SDK Generation
      • 1
        API Mocking
      CONS OF RAML
        Be the first to leave a con

        related RAML posts

        gRPC logo

        gRPC

        716
        836
        43
        A high performance, open-source universal RPC framework
        716
        836
        + 1
        43
        PROS OF GRPC
        • 17
          Higth performance
        • 10
          Easy setup
        • 9
          The future of API
        • 4
          Contract-based
        • 3
          Polyglot
        CONS OF GRPC
          Be the first to leave a con

          related gRPC posts

          Shared insights
          on
          Kafka
          gRPC
          at

          By mid-2015, Uber’s rider growth coupled with its cadence of releasing new services, like Eats and Freight, was pressuring the infrastructure. To allow the decoupling of consumption from production, and to add an abstraction layer between users, developers, and infrastructure, Uber built Catalyst, a serverless internal service mesh.

          Uber decided to build their own severless solution, rather that using something like AWS Lambda, speed for its global production environments as well as introspectability.

          See more
          REST logo

          REST

          20
          140
          0
          A software architectural style
          20
          140
          + 1
          0
          PROS OF REST
          • 2
            Popularity
          CONS OF REST
            Be the first to leave a con

            related REST posts

            Amazon API Gateway logo

            Amazon API Gateway

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

            related Amazon API Gateway posts

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