How Postman Engineering Does Microservices Today

Postman has evolved its microservices approach since its initial challenges, now implementing a system that emphasizes domain-driven squads and consumer-driven contract testing. The engineering team, consisting of over 100 engineers across multiple global locations, organizes itself into squads following domain-driven design principles, each focusing on specific domains like Identity, while independently managing their roadmaps and processes. This structure, influenced by Conway’s Law, promotes API-first design and development, and each squad operates with a degree of autonomy, choosing their tools and processes. The development process involves creating a team workspace for new services, drafting Postman Collections as blueprints, and engaging stakeholders for feedback, leading to a contract for parallel development. Consumer-driven contract tests are integrated into continuous integration pipelines to ensure robust deployments, complemented by continuous monitoring to detect issues post-deployment. This iterative process allows Postman to quickly adapt and improve their services while addressing coordination challenges between squads and managing domain responsibilities.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.