Alternatives to Pact logo

Alternatives to Pact

act, Postman, Amazon API Gateway, Istio, and Insomnia REST Client are the most popular alternatives and competitors to Pact.
23
35
+ 1
0

What is Pact and what are its top alternatives?

It is a code-first tool for testing HTTP and message integrations using contract tests. Contract tests assert that inter-application messages conform to a shared understanding that is documented in a contract. Without contract testing, the only way to ensure that applications will work correctly together is by using expensive and brittle integration tests.
Pact is a tool in the Microservices Tools category of a tech stack.
Pact is an open source tool with 217 GitHub stars and 94 GitHub forks. Here’s a link to Pact's open source repository on GitHub

Top Alternatives to Pact

  • act

    act

    Rather than having to commit/push every time you want test out the changes you are making to your .github/workflows/ files (or for any changes to embedded GitHub actions), you can use this tool to run the actions locally. The environment variables and filesystem are all configured to match what GitHub provides. ...

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

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

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

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

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

Pact alternatives & related posts

act logo

act

5
19
0
Run your GitHub Actions locally
5
19
+ 1
0
PROS OF ACT
    Be the first to leave a pro
    CONS OF ACT
      Be the first to leave a con

      related act posts

      Postman logo

      Postman

      64.5K
      52.5K
      1.8K
      Only complete API development environment
      64.5K
      52.5K
      + 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
        Option to run scrips
      • 7
        Collections
      • 7
        Global/Environment Variables
      • 6
        Dead simple and useful. Excellent
      • 6
        Dark theme easy on the eyes
      • 6
        Shareable Collections
      • 5
        Great integration with newman
      • 5
        Awesome customer support
      • 4
        Documentation
      • 4
        The test script is useful
      • 4
        Simple
      • 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
      • 2
        API-network
      • 2
        Mocking API calls with predefined response
      • 2
        I'd recommend it to everyone who works with apis
      • 1
        Graph
      • 1
        Pre-request Script and Test attributes are invaluable
      • 1
        Continuous integration using newman
      • 1
        Now supports GraphQL
      • 1
        Postman Runner CI Integration
      • 1
        Easy to setup, test and provides test storage
      • 0
        Runner
      • 0
        <a href="http://fixbit.com/">useful tool</a>
      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 · 2.1M 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 · 2.1M 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

      1.1K
      853
      42
      Create, publish, maintain, monitor, and secure APIs at any scale
      1.1K
      853
      + 1
      42
      PROS OF AMAZON API GATEWAY
      • 36
        AWS Integration
      • 5
        Websockets
      • 1
        Serverless
      CONS OF AMAZON API GATEWAY
      • 1
        Less expensive
      • 1
        No websocket broadcast

      related Amazon API Gateway posts

      A Luthra
      VP Software Engrg at Reliant · | 3 upvotes · 444.5K 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
      Istio logo

      Istio

      649
      1.2K
      43
      Open platform to connect, manage, and secure microservices, by Google, IBM, and Lyft
      649
      1.2K
      + 1
      43
      PROS OF ISTIO
      • 12
        Zero code for logging and monitoring
      • 8
        Service Mesh
      • 7
        Great flexibility
      • 4
        Ingress controller
      • 3
        Resiliency
      • 3
        Easy integration with Kubernetes and Docker
      • 3
        Full Security
      • 3
        Powerful authorization mechanisms
      CONS OF ISTIO
      • 11
        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
      Insomnia REST Client logo

      Insomnia REST Client

      578
      477
      37
      The most intuitive cross-platform REST API Client 😴
      578
      477
      + 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
      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
        KongKongIstioIstio

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

        See more
        OpenAPI logo

        OpenAPI

        323
        265
        0
        Allows the owner of a network-accessible service to give universal access
        323
        265
        + 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 · 229.2K 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
            Paw logo

            Paw

            204
            253
            165
            The ultimate REST client for Mac
            204
            253
            + 1
            165
            PROS OF PAW
            • 46
              Great interface
            • 38
              Easy to use
            • 25
              More stable and performant than the others
            • 16
              Saves endpoints list for testing
            • 13
              Supports environment variables
            • 12
              Integrations
            • 9
              Multi-Dimension Environment Settings
            • 4
              Paste curl commands into Paw
            • 2
              Creates code for any language or framework
            CONS OF PAW
            • 3
              It's not free
            • 2
              MacOS Only

            related Paw 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