Schema Definition Performance / Best Practice
Is it considered bad practice to have one massive client / schema definition for my whole project that is imported everywhere, or should I be creating a client with small smaller sub-schemas for each module? are there any significiant performance benefits to the latter?
My project has about 20 tables with relations and am running into performance problems in my development environment (nextjs takes a long time to build routes in dev mode).
Is splitting out multiple smaller schemas something that is likely to help much?
EDIT: Performace seems to be a nextjs issue rather than drizzle, sorry.
1 Reply
This is a nextjs app router problem that's been going on for quite some time