service-oriented-architecture

Split a monolithic tRPC backend by distributing procedures across independent services using a shared initTRPC instance and a type-only gateway to merge AppRouter types. A custom client-side link routes requests to different service URLs based on path segments.

A type-only gateway in tRPC service-oriented architecture merges routers for full AppRouter type inference without running a central server. It provides end-to-end type safety across distributed services while avoiding a monolithic routing bottleneck.

Route tRPC client requests to multiple backend services by implementing a custom client-side link. This link inspects the first path segment of the procedure call and directs the network request to the corresponding standalone server URL.

You need a shared server-lib package to maintain type safety across tRPC microservices. It exports a shared initTRPC instance to ensure consistent procedure and router definitions are used across all independently deployed services.

Scale a tRPC backend using multi-service routing when procedures need distributed deployment for independent scaling. It suits large applications where splitting domains like user management and notifications reduces monolithic bottlenecks.