Tips/Tricks for large scale create-t3-turbo projects?
Curious if anyone has experience using create-t3-turbo for a large scale app/website and ran into any footguns or things they would've done differently. Specifically wondering about the separation of concerns between react native and the next.js app. There is alot of docs about scalable next, but adding native does bring about some need for planning.
4 Replies
When you say large scale do you mean in users or in functionality i.e. data driven app with lots of tables etc?
Yup, second one, in functionality. Lots of accumulation of data. graphs, tables, calendars. So performance is definitely a concern
I'm currently building a warehouse management app with T3app which is an extension /rewrite of the in production site that has a few hundred pages and over 100 database tables a lot with 6 digit row counts. Pretty small in the whole scheme of things but a decent amount where I had to think about this.
Ultimately I think it just boils down to how you like to manage your DB calls and if you need to micromanage server load. Having an express or whatever backed makes sense if you are concurrently developing native and web and need something agnostic. You could use T3app with an Express backend if you wanted or set up next api routes that the native app could hit But... The T3 experience is meant for speed, so you can get things done. It links the frontend and backend using trpc because it's fast to dev with. Doesn't mean you cant build an API with it or do enterprise scale things but the ideology is move quick.
I'd skip prisma though.
For clarity. It will scale to any size but at a certain size you may not be using the things that are it's selling points or will want to roll your own. But that's fine at it's core it's just a React framework with file based routing, you can do whatever. Or if you are a super nerd ditch react and learn leptos/rust
Learn verival slicing of features
Vertical *