When comparing Postman vs dejavu, the Slant community recommends Postman for most people. In the question“What are the best Elasticsearch GUI clients?” Postman is ranked 3rd while dejavu is ranked 6th.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Free
Pro Flexible and powerful
Can easily add/remove parameters, headers, tests and more. Displays all the info you would want in a partitioned way so you can track exactly what you want. Able to save request and run them in bulk for testing real-user scenarios very efficiently.
Pro Clear interface
The interface of the program is clean and intuitive. Almost all features are accessible through a single click.
Pro Two versions of apps are available
Packaged app and an in-browser app are available for Google Chrome.
Pro Excellent user feedback loop
Postman is very responsive to users and listens to user feedback.
Pro Dark theme
Pro Free and open source
Dejavu is completely free and open source and it's released under the MIT License.
Pro Search preview
Can generate a functional react web app for search preview for seeing dataset relevancy.
Pro Availability
Dejavu is available as a web app, a docker image or as a chrome extension.
Pro Can create filtered and query views
Import data that can be browsed to see filtered and query views of it.
Pro Quick UI Preview
Allows you to quickly put together a search application from one index.
Pro Supports importing JSON and CSV files
Pro Export data in JSON and CSV formats
Pro Has infinite scroll with progressive loading of rows
Pro Supports local filters
Cons
Con Version 8.x killed Postman - some problem related to "Teams"
Postman is forcing everybody to move their data to the cloud.
Con Insecure off-premise storage
To properly use this with full development and testing it stores API details, including security, in an off-site storage managed by Postman. It also stores details about employees, teams they are members of, and projects they are working on.
This makes it inappropriate for any organization that is required to exercise a high level of security hygiene when developing software products. This issue may be compounded by the lack of details concerning the geolocation of data storage.
Con Proprietary, closed source software
Not free and open source.
Con Resource hog
Con Bloated & cluttered
Bloated and cluttered, it's quicker to just have a js/ts template available to run some requests.
Con Limited free APIs
Con Doesn't work right with localized queries
Con Does not support Proxy authentication
Con Does not work with aliases
It would be more awesome if it could also consume aliases