Item: Postman
Rating: 9
Author: Verified User

Use Cases and Deployment Scope

Our platform uses a lot of microservices. It has a lot of REST API for various purposes such as to get the information about what task is being currently handled by the CI, is there something which seems to be failing, etc. In order to address all of these problems, we use Postman to query the current state of our microservices.

Pros and Cons

Ability to store commands
Integrates with Jenkins

Faster bug fixes

Return on Investment

We are using the free version.

Alternatives Considered

I have used curl command which pretty much does the same in an unordered fashion. Postman has organization to it, with an ability to store commands in a fashion where it just becomes easy to use it.

Key Insights

Do you think Postman delivers good value for the price?

Yes

Are you happy with Postman's feature set?

Yes

Did Postman live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Postman go as expected?

Yes

Would you buy Postman again?

Yes

Other Software Used

MongoDB, Kubernetes, Amazon Route 53

Likelihood to Recommend

If you are planning to run different test cases on different environments and it is kind of a repetitive job, I believe it is always better to use Postman since it just gives you an amazing, resilient UI. Its integration with Jenkins makes it easier to execute tests within the build systems itself. Also, they have a Newman feature which enables running Postman form systems that dont have GUI.

Postman: organize and improve efficiency of API development.

Overall Satisfaction with Postman