We moved Railway's frontend off Next.js. Builds went from 10+ mins to under two
blog.railway.com - 68 poäng - 37 kommentarer - 16426 sekunder sedan
Kommentarer (15)
- maccard - 8979 sekunder sedanIt’s absolutely mind boggling to me that we have gotten to a point that building a web frontend takes longer than compiling the Linux kernel..
- miyuru - 4887 sekunder sedanI just tried their domains page it took 10.8MB of data and took 2s for the DOM to be ready.
page actually took 17s to fully render with multiple shift changes.
all to render a domain search bar similar to google home page.
- SilverSlash - 5578 sekunder sedanA lot of the LLMs are very familiar with next.js and vercel is also aggressively building an ecosystem around their tooling for LLMs. So I wonder if this problem will only be exacerbated when everyone using LLMs is strongly nudged (forced) to use next?
- tgdn - 8245 sekunder sedanWe went through a very similar migration. Had a Next.js landing page and a separate TanStack Router SPA - consolidated both into a single Vite + TanStack Start app. Same experience with build times and the architecture mismatch: our app is heavily client-side with real-time state, and fighting Next.js's server-first assumptions wasn't worth it. TanStack Router's type-safe routing and file-based route generation have been great.
- UserMark - 7457 sekunder sedanI have a Nextjs heavy app which takes around 7 minutes currently. But I've been thinking of moving away from next for a long time now. TanStack seems to be a good fit. This gives me a bit more confidence in just doing it.
- wouldbecouldbe - 6461 sekunder sedanThe irony is deploying NextJS on the railway platform is super slow since they use containers, on Vercel 2 min is like 12 min on railway, deployments on a vps are only like 20 seconds.
*I know this is just build time, so this is different then their deployement time
- Hendrikto - 5804 sekunder sedanTwo minutes is still way too long. What are we doing? This is ridiculous.
- jspaetzel - 8627 sekunder sedanIncredible that the builds were ever 10min. How far things have regressed.
- fnoef - 5711 sekunder sedan:suprised_pikachu_face:
Is the quality of software engineers really dropped that low that people get excited when they move off from "heavy bloated" frameworks to lighter alternatives? Or is this just SEO farming garbage to position the company higher in search results?
- samwreww - 6981 sekunder sedanThey don't even mention the Next.js version used - where they using Turbopack or not?
- huksley - 6625 sekunder sedanAnyone tried to use vinext from Cloudflare in production? Might be faster.
But seriously, not sure why NextJS builds take so much, we are using stable and functional pages router in DollarDeploy and it is still takes too much time to build.
- mlnj - 8561 sekunder sedanThis is one of the most frustrating thing about working with NextJS. There seems to be no way to improve the speed of building the app.
- mememememememo - 5870 sekunder sedanWait till you use HTMX!
- Paul20261 - 6221 sekunder sedan[dead]
- mellosouls - 9041 sekunder sedanReminder, as its not mentioned:
Next.js is produced by Vercel, a competitor to Railway.
Nördnytt! 🤓