policyengine-api-v2

A microservices monorepo for API development separates logic into distinct service folders like api-full, api-simulation, and api-tagger, alongside shared utilities. This layout streamlines dependency management, OpenAPI generation, and Docker-based local development across multiple services.

Managing Python dependencies in a microservices monorepo is optimized using uv-based tooling. This approach provides fast, reliable package management across shared utilities and individual services, ensuring consistent local development and deployment environments.

Generating OpenAPI specs for multiple microservices involves using built-in client tooling within the monorepo blueprint. This streamlines API integration by automatically producing documentation and client libraries from the api-full, api-simulation, and api-tagger services.

Yes, Supabase can be used as a PostgreSQL backend for microservices. It provides persistent data storage and built-in authentication, integrating seamlessly with a Docker-based local development setup to support scalable API architectures.

Yes, the monorepo blueprint includes a clear migration path from v1 architecture. It provides roadmap visibility for contributors, ensuring a structured transition when moving existing APIs to the new api-full, api-simulation, and api-tagger service structure.