←back to thread

95 points vednig | 1 comments | | HN request time: 0.212s | source
Show context
jonplackett ◴[] No.42199044[source]
This is very cool.

Do you have any ideal the cost difference of running this VS NextJS for any particular workload?

I use NextJS on Vercel for so many projects but mostly smaller things since I know it can get very expensive after scaling up.

replies(1): >>42199421 #
greyskull ◴[] No.42199421[source]
The biggest cost for us on Vercel (several hundred dollars a month) was Image Optimization, and that was because the app was being majorly inefficient with images, in part due to some default behavior in Next.js that we found unfriendly [0], and in part due to negligence. That being said, it wasn't "cheap" by any means outside of that, still hundreds a month for something that I would not consider a high traffic application (I wish I could remember more specific numbers).

Migrating to OpenNext using SST, I think we got the bills for compute and asset serving down to like $15/day or something (granted, we spent expensive engineer time on the migration).

[0] https://nextjs.org/docs/app/api-reference/components/image#s...

replies(2): >>42199610 #>>42202675 #
dbbk ◴[] No.42202675[source]
There's pretty much no reason to use Vercel's image optimization, just spend 30 minutes setting up Cloudflare Images and call it a day
replies(1): >>42216871 #
1. greyskull ◴[] No.42216871[source]
I agree.