Google Cloud Endpoints vs Postman

Overview

Postman

Stacks96.1K

Followers82.5K

Votes1.8K

Forks0

Google Cloud Endpoints

Stacks36

Followers149

Votes1

Google Cloud Endpoints vs Postman: What are the differences?

Introduction

Google Cloud Endpoints and Postman are both popular tools used in API development and testing. While they serve similar purposes, there are key differences between the two that make them distinct.

API Management and Deployment: Google Cloud Endpoints offers a comprehensive API management solution that allows you to easily deploy, monitor, and control access to your APIs. It provides features like API key authentication, quota enforcement, and automatic deployment to Google Cloud Platform. On the other hand, Postman primarily focuses on API testing and documentation, providing a user-friendly interface for creating and sending API requests. It does not provide the same level of deployment and management features as Google Cloud Endpoints.
Integration with Google Cloud Platform: Google Cloud Endpoints seamlessly integrates with other services and tools within the Google Cloud Platform ecosystem. It works well with services like Cloud Run, Cloud Functions, and Kubernetes Engine, allowing you to easily expose your APIs as serverless functions or containers. Postman, on the other hand, is a standalone tool that can be used with any API, regardless of the underlying infrastructure or platform.
SDK Generation: Google Cloud Endpoints provides SDK generation capabilities, allowing you to automatically generate client libraries for different programming languages based on your API specification. This makes it easier for developers to consume your APIs and reduces the amount of boilerplate code they need to write. Postman does not offer this feature and requires developers to manually handle API consumption in their chosen programming language.
Collaboration and Team Work: Postman provides a collaborative workspace that allows teams to work together on API development and testing. Teams can easily share collections, environment variables, and tests with each other, promoting collaboration and ensuring consistency in API development. While Google Cloud Endpoints does not offer a dedicated collaboration workspace, it integrates with other collaboration tools like Google Cloud Source Repositories, allowing teams to work together on API codebases.
Pricing Model: Google Cloud Endpoints follows a pricing model based on API call volume and other factors within the Google Cloud Platform pricing structure. The cost varies depending on factors like the number of requests, the amount of data transferred, and any additional services used. Postman, on the other hand, offers flexible pricing plans based on team size and usage requirements, with options for free individual accounts and paid team plans.
Documentation and API Reference: Google Cloud Endpoints automatically generates API documentation and provides an API Explorer to easily test your APIs while working with Google Cloud Platform. Postman also includes features for documenting APIs, generating collections, and sharing them with others. However, the documentation and API reference capabilities of Google Cloud Endpoints are more tightly integrated with the overall Google Cloud Platform ecosystem, making it easier to manage and maintain your API documentation within the platform.

In summary, Google Cloud Endpoints and Postman differ in terms of API management and deployment capabilities, integration with Google Cloud Platform, SDK generation, collaboration features, pricing model, and documentation capabilities.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Postman, Google Cloud Endpoints

Jagdeep

Tech Lead at Founder and Lightning

May 6, 2019

Reviewon

Postman

I use Postman because of the ease of team-management, using workspaces and teams, runner, collections, environment variables, test-scripts (post execution), variable management (pre and post execution), folders (inside collections, for better management of APIs), newman, easy-ci-integration (and probably a few more things that I am not able to recall right now).

411k views411k

Comments

StackShare

May 1, 2019

Needs advice

From a StackShare Community member: "I just started working for a start-up and we are in desperate need of better documentation for our API. Currently our API docs is in a README.md file. We are evaluating Postman and Swagger UI. Since there are many options and I was wondering what other StackSharers would recommend?"

382k views382k

Comments

Stephen

Artificial Intelligence Fellow

Feb 4, 2020

Decided

Postman supports automation and organization in a way that Insomnia just doesn't. Admittedly, Insomnia makes it slightly easy to query the data that you get back (in a very MongoDB-esque query language) but Postman sets you up to develop the code that you would use in development/testing right in the editor.

361k views361k

Comments

Detailed Comparison

Postman	Google Cloud Endpoints
It is the only complete API development environment, used by nearly five million developers and more than 100,000 companies worldwide.	An NGINX-based proxy and distributed architecture give unparalleled performance and scalability. Using an Open API Specification or one of our API frameworks, Cloud Endpoints gives you the tools you need for every phase of API development and provides insight with Google Cloud Monitoring, Cloud Trace, Google Cloud Logging and Cloud Trace.
Compact layout;HTTP requests with file upload support;Formatted API responses for JSON and XML;Image previews;Request history;Basic Auth, OAuth 1.0, OAuth 2.0, and other common auth helpers;Autocomplete for URL and header values;Key/value editors for adding parameters or header values. Works for URL parameters too.;Use environment variables to easily shift between settings. Great for testing production, staging or local setups.;Keyboard shortcuts to maximize your productivity;Automatically generated web documentation;Mock servers hosted on Postman’s cloud;API monitoring run from Postman cloud	-
Statistics
GitHub Forks 0	GitHub Forks -
Stacks 96.1K	Stacks 36
Followers 82.5K	Followers 149
Votes 1.8K	Votes 1
Pros & Cons
Pros 490 Easy to use 369 Great tool 276 Makes developing rest api's easy peasy 156 Easy setup, looks good 144 The best api workflow out there Cons 10 Stores credentials in HTTP 9 Bloated features and UI 8 Cumbersome to switch authentication tokens 7 Poor GraphQL support 5 Expensive	Pros 1 Android Integration
Integrations
HipChat Keen Slack Dropbox Datadog PagerDuty Bigpanda Microsoft Teams Newman VictorOps	Google App Engine Google Compute Engine Google Kubernetes Engine

What are some alternatives to Postman, Google Cloud Endpoints?

Swagger UI

Swagger UI is a dependency-free collection of HTML, Javascript, and CSS assets that dynamically generate beautiful documentation and sandbox from a Swagger-compliant API

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.

Apiary

It takes more than a simple HTML page to thrill your API users. The right tools take weeks of development. Weeks that apiary.io saves.

Karate DSL

Combines API test-automation, mocks and performance-testing into a single, unified framework. The BDD syntax popularized by Cucumber is language-neutral, and easy for even non-programmers. Besides powerful JSON & XML assertions, you can run tests in parallel for speed - which is critical for HTTP API testing.

ReadMe.io

It is an easy-to-use tool to help you build out documentation! Each documentation site that you publish is a project where there is space for documentation, interactive API reference guides, a changelog, and much more.

Appwrite

Appwrite's open-source platform lets you add Auth, DBs, Functions and Storage to your product and build any application at any scale, own your data, and use your preferred coding languages and tools.

Runscope

Keep tabs on all aspects of your API's performance with uptime monitoring, integration testing, logging and real-time monitoring.

Insomnia REST Client

Insomnia is a powerful REST API Client with cookie management, environment variables, code generation, and authentication for Mac, Window, and Linux.

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.

Docusaurus

Docusaurus is a project for easily building, deploying, and maintaining open source project websites.

Related Comparisons

Google Cloud Endpoints vs Postman: What are the differences?

Introduction

Google Cloud Endpoints and Postman are both popular tools used in API development and testing. While they serve similar purposes, there are key differences between the two that make them distinct.

API Management and Deployment: Google Cloud Endpoints offers a comprehensive API management solution that allows you to easily deploy, monitor, and control access to your APIs. It provides features like API key authentication, quota enforcement, and automatic deployment to Google Cloud Platform. On the other hand, Postman primarily focuses on API testing and documentation, providing a user-friendly interface for creating and sending API requests. It does not provide the same level of deployment and management features as Google Cloud Endpoints.
Integration with Google Cloud Platform: Google Cloud Endpoints seamlessly integrates with other services and tools within the Google Cloud Platform ecosystem. It works well with services like Cloud Run, Cloud Functions, and Kubernetes Engine, allowing you to easily expose your APIs as serverless functions or containers. Postman, on the other hand, is a standalone tool that can be used with any API, regardless of the underlying infrastructure or platform.
SDK Generation: Google Cloud Endpoints provides SDK generation capabilities, allowing you to automatically generate client libraries for different programming languages based on your API specification. This makes it easier for developers to consume your APIs and reduces the amount of boilerplate code they need to write. Postman does not offer this feature and requires developers to manually handle API consumption in their chosen programming language.
Collaboration and Team Work: Postman provides a collaborative workspace that allows teams to work together on API development and testing. Teams can easily share collections, environment variables, and tests with each other, promoting collaboration and ensuring consistency in API development. While Google Cloud Endpoints does not offer a dedicated collaboration workspace, it integrates with other collaboration tools like Google Cloud Source Repositories, allowing teams to work together on API codebases.
Pricing Model: Google Cloud Endpoints follows a pricing model based on API call volume and other factors within the Google Cloud Platform pricing structure. The cost varies depending on factors like the number of requests, the amount of data transferred, and any additional services used. Postman, on the other hand, offers flexible pricing plans based on team size and usage requirements, with options for free individual accounts and paid team plans.
Documentation and API Reference: Google Cloud Endpoints automatically generates API documentation and provides an API Explorer to easily test your APIs while working with Google Cloud Platform. Postman also includes features for documenting APIs, generating collections, and sharing them with others. However, the documentation and API reference capabilities of Google Cloud Endpoints are more tightly integrated with the overall Google Cloud Platform ecosystem, making it easier to manage and maintain your API documentation within the platform.

Google Cloud Endpoints vs Postman

Overview