platformatic-runtime

Platformatic Runtime orchestrates multiple Fastify services in a monorepo into a single process using watt.json for environment mapping and pnpm workspaces for shared configuration and consistent runtime behavior.

Inter-service communication in Platformatic Runtime uses in-process fetch calls with plt.local hostnames to route requests safely without network overhead, ensuring efficient interaction between orchestrated services.

The standard service entry point pattern for a Platformatic Runtime project uses a centralized create() pattern, enforcing best practices for lifecycle management and standardized testing strategies across services.

Testing strategies for microservices in a Platformatic Runtime separate unit and integration tests by leveraging the standardized create() service entry point pattern to isolate service logic from runtime orchestration.

Yes, Platformatic Runtime supports pnpm workspaces for multi-service architectures, applying shared monorepo patterns and centralized runtime configuration to manage multiple Node services effectively.

Using Platformatic Runtime instead of running microservices independently ensures consistent runtime behavior, shared configuration, and safe in-process inter-service communication without network overhead.