nikfp
Multiple TRPC endpoints on same API, with discrete clients? Any gotchas?
I'm also kind of a beginner tbf, I used it for a little while just to see how it worked, and then started using form actions in Sveltekit when those came around. This was about a year ago, and I didn't get a ton of time with trpc. My biggest concern is committing to it, then finding out later that it's bogging down development earlier than I'm ready to start breaking the app apart into discrete services to get the perf gains.
We'll see, all opinions on the matter are welcome.
12 replies
Multiple TRPC endpoints on same API, with discrete clients? Any gotchas?
what I was hoping for was having the multiple routers isolated per API route, so when you were working on the
estimating route you would only have access to the trpc procedures for that route. Just a level of isolation for development, so futures devs (ahem me) don't get confused and start cross cutting concerns. Also not sure if this holds water, but having separated routers might mean less load on the language server so I might be able to scale the project a bit more before trpc starts to bog down.
All just conjecture at the moment, but I'm curious how folks are doing things.12 replies