3 ms·
“We received an unexpected $2,000 bill from Vercel due to high API usage from a single user” Skill issue. Testing APIs became a nightmare, because we had a lo
by joshcsimmons 2y ago
“We received an unexpected $2,000 bill from Vercel due to high API usage from a single user”
Skill issue.
Testing APIs became a nightmare, because we had a lof of server actions mixed with api routes.
Sounds like you designed the app poorly.
Build times got so slow it felt like watching paint dry.
Heard but is there any situation where you’d a sub 3 minute deploy.
Local dev was brutal - every tiny change triggered a full SSR reload.
I have never noticed this as an issue across any Next app of any size that I’ve worked on.
I agree that next probably doesn’t scale but it’s pretty good for 0-to-1 without having to worry about setting up routing, tailwind, basic API etc