tRCP beginner questions
I am very new to tRPC and it is too good to by true but there are some general and basics questions I have:
1. tRCP couples the client and the server together, does this mean that you can not consume a tRCP server/endpoint with different clients that you develop separately but with the same type experience?
2. are there tRCP server implementations for other languages? (Rust, Python)
3. does tRCP offers a pattern to query children the way you want or with a separate query?
4. does tRCP offers a pattern or a default way to solve the n + 1 problem?
5. is it true that if you have a tRCP project does not scale well, and that you sooner or later will migrate to graphQL?
6. are you able to select only fields you like and nothing more?
7. what protocol does tRPC uses underneath?
I mean can curl tRPC or can you use POSTMAN to test it?
Does it use REST in the background?
8. is it normal/by design that T3 forces you to join client server and client code to one single server?
is it possible to split these two, with T3, and have the client and the server as two different servers? If not why?
3 Replies
1. as long you can safely infer the trpc types, you can use from any client, even multiple clients
2. trpc is based around the typescript server inference, so its impossible for other languages without the same feature to work like that
3. that is graphql, making queries against a graph, trpc is just a typesafe way of calling a query/mutation
4. the same as 3, if you would have a n+1 on other services, trpc wont solve that for you
5. what you define as scaling well?
Theo - t3․gg
YouTube
Does YOUR Tech Scale?
We talk about "scale" a lot around these parts, but I feel like we often miss the point. Scale means a lot of different things. I did my best here to break that down.
#t3stack #fullstack #webdevelopment
ALL MY VIDEOS ARE POSTED EARLY ON PATREON https://www.patreon.com/t3dotgg
Everything else (Twitch, Twitter, Discord & my blog): https://t3.gg...