Building large-surface APIs in TSS
I'm building out a service that needs lots and lots of public facing API endpoint. Probably around ~70.
I love me some file routing - but I think I'll regret it. Most of these routes share common resources and I'm envisioning quite a lot of
createFileRoute overhead.
What's the best call here? Spin up a seperate project for the API? Throw a hono server in a catch-all (does that even work?)
Any advice appreciated!1 Reply
exotic-emerald•7mo ago
what kind of overhead?
about hono, search this discord. has been discussed