Running migrations in server-less (edge) land??
According to the docs:
If this is deployed in a server-less land with something like sveltekit that runs on the edge.. Does that mean that drizzle ORM will query the database on every single request as the database controller gets re-initialised on every http request?
If so, I'm guessing it would be cleaner to have the deployment run as part of the CI/CD and run it as a script?
Cheers
(context)
I'm running sveltekit on vercel with a vercel edge postgres. I susepct when my sveltekit app is invoked for each page request, the drizzleOrm will get initalised and run the await migrate which has some overhead.
If this is deployed in a server-less land with something like sveltekit that runs on the edge.. Does that mean that drizzle ORM will query the database on every single request as the database controller gets re-initialised on every http request?
If so, I'm guessing it would be cleaner to have the deployment run as part of the CI/CD and run it as a script?
Cheers
(context)
I'm running sveltekit on vercel with a vercel edge postgres. I susepct when my sveltekit app is invoked for each page request, the drizzleOrm will get initalised and run the await migrate which has some overhead.
