> import { sql } from '@vercel/postgres'; Careful here. You'd be building a vercel-specific API into the middle of your data access stack. That might be fine..

> import { sql } from '@vercel/postgres'; Careful here. You'd be building a vercel-specific API into the middle of your data access stack. That might be fine... e.g., if it has a limited/specific use or lifetime, so that you know you won't get stuck. But otherwise, use a standard, portable client. The docs say you can use any postgres client, so you should be able to choose whatever you prefer.