<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postman on VisorCraft News</title><link>https://www.visorcraft.com/news/tags/postman/</link><description>Recent content in Postman on VisorCraft News</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 12 Aug 2026 10:00:00 -0500</lastBuildDate><atom:link href="https://www.visorcraft.com/news/tags/postman/index.xml" rel="self" type="application/rss+xml"/><item><title>Mongrel vs Postman: API Work Beside the Data and Infrastructure</title><link>https://www.visorcraft.com/news/2026/08/mongrel-vs-postman-api-database-workbench/</link><pubDate>Wed, 12 Aug 2026 10:00:00 -0500</pubDate><guid>https://www.visorcraft.com/news/2026/08/mongrel-vs-postman-api-database-workbench/</guid><description>&lt;p&gt;When an investigation spans more than one system, context switching becomes the bottleneck. You open a browser tab for the API documentation, a separate window for your database client, another for the terminal that has the right SSH session, and somewhere in there is Postman with your collection of saved requests. Each window knows nothing about the others. Mongrel takes a different approach by placing API requests inside a workbench that already has the database connections, terminal sessions, container views, and file browsing that engineers need when they are debugging a service, validating a migration, or tracing a failure across boundaries.&lt;/p&gt;</description></item></channel></rss>