When should a UK project use tRPC instead of REST?

tRPC is right when: (1) the frontend and backend are both TypeScript and in the same monorepo, (2) the API is never consumed by external parties (no FCA COBS disclosure requirement, no partner integrations), (3) the team wants to avoid maintaining a separate OpenAPI schema. In practice: tRPC for internal admin dashboards, operator portals, and internal tooling. REST for any API exposed to external parties, consumed by mobile apps built by a separate team, or required to satisfy regulatory disclosure. ClickMasters uses tRPC for internal services and REST for all external APIs.

Can tRPC be used for NHS DTAC applications?

tRPC can be used for internal application layers (frontend → backend in the same Next.js application) in NHS DTAC systems. However: NHS DTAC Domain 4 (Interoperability) requires FHIR R4-compliant external APIs for any patient data exchange with other NHS systems. tRPC is not a substitute for FHIR R4. ClickMasters uses tRPC for internal application queries and FHIR R4 REST for all external NHS system integrations.

Trpc Vs Rest Vs Graphql Typescript Uk

tRPC vs REST vs GraphQL — TypeScript API Architecture (2025)

Updated: October 20259 min read

🇬🇧 UK💷 GBP📊 Comparison🔒 UK GDPR⚖️ UK Law

Direct Answer

tRPC is the right choice for full-stack TypeScript projects where the frontend and backend are in the same codebase or organisation — end-to-end type safety without an OpenAPI schema, zero code generation, and exceptional developer experience. REST with OpenAPI remains the standard for UK external APIs (FCA COBS disclosure, NHS FHIR R4, GDS Service Standard). GraphQL for complex internal data aggregation. The decision depends entirely on who consumes the API. TypeScript API architecture choice affects UK regulatory compliance (REST for external FCA/NHS/GDS APIs) and developer productivity (tRPC for internal full-stack TypeScript).

Factor	tRPC	REST + OpenAPI 3.0	GraphQL
FCA COBS API disclosure	Not applicable (internal only)	✅ OpenAPI satisfies FCA COBS	Schema available but non-standard
NHS FHIR R4	Not applicable	✅ FHIR IS a REST standard	Not FHIR-compatible
GDS Service Standard API	Not applicable	✅ GDS mandates REST + OpenAPI	Not standard in GDS
External API consumers (partners)	Not applicable — internal only	✅ Standard external API	Developer experience varies
Full-stack TypeScript (same codebase)	✅ Best — zero schema, full type safety	Schema required — more boilerplate	Type generation required
Developer experience (same org)	✅ Best — autocomplete, refactoring	Good — OpenAPI generation	Good — code generation required
Type safety without codegen	✅ Native — zero codegen	Requires OpenAPI codegen	Requires GraphQL codegen
UK GDPR data minimisation	Good — procedure-based queries	✅ Explicit — OpenAPI documents all fields	✅ Query exactly needed fields
ClickMasters use	Internal full-stack TypeScript apps	✅ All external UK regulated APIs	Complex multi-source internal APIs