Loved the idea of managed protections and automatic builds. But in practice I’m having a difficult time getting Vercel working how I’d expect:
Using vercel dev locally is giving slow db (mysql) requests. 500ms vs 2ms on node. That means waiting 4s+ every time I reload, that is instantaneous with node. Is this expected behaviour?
The production db requests are faster, but only after an initial ‘spin up’ slow first load. (location for vercel and db are both central europe). Is this expected behaviour with a serverless setup?
Headaches working out when project variables are handled through .env files or through the vercel dashboard. Seems counterintuitive and the UI for adding/removing is a pain. Still don’t really understand this and testing has seemed random.
Saving temp files is not possible? Writing to s3 before reading is slow (for example playing a short audio file). Is there a work around for this?
I’ve spent two days trying to make this work for my simple react/mysql web app, and I’m wondering if I should cut my losses and go back to self-managed AWS.
Any wisdom on the above? Did I take a wrong turn towards Vercel for my needs (i.e. a site with a db)?
Many thanks