Postman

Postman

Utilities / Application Utilities / API Tools
Software Solution Architect at Supernova·
Needs advice
on
PostmanPostman
and
RapidAPIRapidAPI

I'm starting to implement a new full-stack application and adopting an API-first development approach. Right now deciding which of these tools to use to build, mock and track the evolution of my just-born OpenAPI specification.

I'm already familiar with Postman when it comes to consuming ready-to-use implemented API, but not yet with its API-build features. As well as I barely know how FastAPI could help with this goal.

I would like to understand if there'd be a big difference of usage and capabilities between these tools. And any other one that could help on development, test and documentation of a REST API.

Thanks a lot for helping on this!

READ MORE
5 upvotes·157.6K views
Replies (1)
Sr Developer Advocate at Postman·

I'm a little biased because I work at Postman, but I've also used RapidAPI in the past. It won't matter which OpenAPI editor you use, or even if you develop the OpenAPI spec on a third-party platform besides the ones you've mentioned. But I find the automation in Postman far easier to use, and being able to publish your API afterward to everyone makes it a lot easier to let devs find your API and use it right within Postman immediately. The auto-generated docs, the auto-generated client-side samples, and for a handful of languages we even auto-generate some server-side code too.

READ MORE
7 upvotes·10.8K views
Needs advice
on
PostmanPostman
and
SuperTestSuperTest

hello, I have started with Postman and SuperTest,, however I feel like both does a similar task, so please if anyone can advice me regarding what to choose for learning advanced content from both and what makes them different

READ MORE
3 upvotes·159.9K views
Senior Fullstack Developer at QUANTUSflow Software GmbH·

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.
READ MORE
27 upvotes·1 comment·5M views
Kuldip Pipaliya
Kuldip Pipaliya
·
June 17th 2022 at 6:46AM

Amazing approach to building a scalable tech stack !!!

·
Reply
Needs advice
on
Katalon StudioKatalon Studio
and
PostmanPostman

I want to do api testing using any one of this tool. I need to run the test scripts whenever new collection has been given. So if i run my test in Postman, i need to add test scripts manually every time i get new collections. Guide me is there any alternate solutions to reuse my test scripts in postman or which one is best either Katalon Studio or postman..

READ MORE
2 upvotes·202K views
Replies (1)
Software Developer at CloudCover·
Recommends
on
Swagger Codegen

Swagger can help you for that which will generate api documentation.

Postman is good for manual testing. Katalon Studio is good for automation api testing.

READ MORE
1 upvote·3.7K views
Technical Lead at Kopa Global Technologies·
Shared insights
at
  • Its used to check and validate all the web services API [ JSON Format] for branded customer mobile apps (iOS & Android) and food delivery app. Postman
READ MORE
1 upvote·126.3K views
CEO at Scrayos UG (haftungsbeschränkt)·

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.

READ MORE
4 upvotes·559.8K views
Shared insights
at
()

Repost

Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku . However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

READ MORE
19 upvotes·2 comments·2.1M views
John Akhilomen
John Akhilomen
·
April 1st 2020 at 3:00PM

I like the tech stack you guys have selected. You guys seem to have it all figured out, and well planned. Good luck!

·
Reply
Ne Labs
Ne Labs
·
March 9th 2020 at 12:34PM

RDBMS like Postgres can also store, index and query schemaless data as JSON fields, while also supporting relations where it makes sense. A document model is actually a downside, since usually data will still have relations, and it makes modeling them inconvenient.

·
Reply