Save Your Time - I deployed Next.js to different services (so you don't have to)
298btw, when I say prod logs, I mean I should be able to go back months in the past and view logs. If a service is $20 a month and they require me to sign up for yet another service to get real log support or be able to use complex queries to find logs in the past containing certain strings, it's a no-go for me personally.
- vercel - best UX, but no built-in prod logs, good metrics ui, pricy, first class next support
- amplify - good ux IMO, lowest latency for me, built-in prod logs via cloudwatch, cache issue as mentioned in prior video, hard to figure out how long endpoints took, parsing endpoint metrics is a joke
- sst - cheapest option, serverless, might require learning IaC, performance similar to vercel? open source so might be slow to adopt new next features, lots of DIY
- digital ocean - seems fastest??, but probably no edge computing, cheap, might get the job done, containerized next =(
- netlify - seems good, beta edge functions, price same as vercel, might as well use vercel
- railway - won't let me use them 🤣 but I do love their service when I used it a while back, but containerized next =(
- render - sucks, didn't work for me
00:00 intro
00:56 AWS Amplify
02:56 sst.dev on AWS
05:22 vercel
08:13 netlify
11:10 digital ocean
13:13 render
13:44 railway
14:46 final thoughts
📘 T3 Stack Tutorial: https://1017897100294.gumroad.com/l/jipjfm
🤖 SaaS I'm Building: https://www.icongeneratorai.com/
💬 Discord: https://discord.gg/4kGbBaa
🔔 Newsletter: https://newsletter.webdevcody.com/
📁 GitHub: https://github.com/webdevcody
📺 Twitch: https://www.twitch.tv/webdevcody
🤖 Website: https://webdevcody.com
🐦 Twitter: https://twitter.com/webdevcody