1. trpcWhen tRPC is not enoughtRPC is excellent for first-party TypeScript clients, but Java, C#, mobile, partners, and public integrations need an explicit contract. That usually means REST plus OpenAPI.
  2. trpctRPC as a driving adaptertRPC can be a clean driving adapter when the domain and use cases stay plain TypeScript. The trick is to keep procedures thin: validate at the boundary, call the use case, and translate the result.
  3. nestjsWhy I stopped using NestJS for DDD and what I use insteadNestJS is productive, but its defaults can quietly turn a DDD codebase into framework-driven application code. Here is the boundary I use now: plain TypeScript in the core, NestJS at the edges.
  4. metaWhat this blog is aboutA short note on the kind of TypeScript, architecture, and engineering writing that belongs on sidlynx.me.