You don't need Next.js

09-Jan-2025 42
I started ComfyDeploy as an open source project (GitHub) - a full stack app with Next.js doing all the heavy lifting for both frontend and backend. We had Drizzle + Server Actions making everything type-safe and neat. It was all good until things started hitting the fan: We received an unexpected $2,000 bill from Vercel due to high API usage from a single user Testing APIs became a nightmare, because we had a lof of server actions mixed with api routes. Build times got so slow it felt like watching paint dry. Local dev was brutal - every tiny change triggered a full SSR reload.
Use coupon code:

JAVASCRIPT

to get 40% discount on our 'The JavaScript Interview Bible' book!
Prepare for your next tech interview with our comprehensive collection of programming interview guides. Covering JavaScript, Ruby on Rails, React, and Python, these highly-rated books offer thousands of essential questions and answers to boost your interview success. Buy our 'Ultimate Job Interview Preparation eBook Bundle' featuring 2200+ questions across multiple languages. Ultimate Job Interview Preparation eBook Bundle