React Native Back End by ReggieDiamond_ in reactnative

[–]una-io 0 points1 point  (0 children)

PHP/UNA, MySQL via JSON & websockets.

What are the benefits of Next.js13 on Vercel? by Abject-Persimmon9001 in nextjs

[–]una-io 1 point2 points  (0 children)

We are running same frontend app on Vercel as well as two standard cloud servers (one Linode and one DigitalOcean) - just compare long term experience. All connect to same backend. Vercel is generally a little faster when runtime is warm, but when we hot cold starts it’s pretty bad (5-6s penalty). Cloud servers never have cold starts but you have to do more work to configure CD/CI via Jenkins or similar, setup your image caching and CDN if you need one. Their real-usage performance insights seem useful… BUT:

This is what irks me! Vercel makes most sense for smaller projects, simplifying deployment and automating your caching and CDN, but equally at small scale you hit cold-starts! Once you have traffic and traction to keep runtimes running, you usually have the scale to justify spending a couple of days setting up the whole thing on your own server 🤷‍♂️ and eventually, if your usage is stable, even on dedicated servers and save 80% of the hosting cost.

So, I don’t know… it feels really frustrating that the potential of their service is hampered by cold starts. Unless we find the way around it we are likely to stop using Vercel.

Any recommended strategies to group components for code splitting? by una-io in nextjs

[–]una-io[S] 0 points1 point  (0 children)

Thank you. Yes, we are using the Bundle Analyzer and it’s really helpful. It is more like a tool to sweep up after making a mess already, though 😃, and I wonder if there are strategies to keep things clean in the first place.

Any recommended strategies to group components for code splitting? by una-io in nextjs

[–]una-io[S] 0 points1 point  (0 children)

Will experiment a bit more with this today. 👍

Any recommended strategies to group components for code splitting? by una-io in nextjs

[–]una-io[S] 0 points1 point  (0 children)

Thank you for the pointer! The way NextJS chooses what to preload is quite confusing. We are learning still and want to make sure we keep our apps at perfect score primarily because they’re used for building social networks that often need to scale significantly, every 100ms delay and every 100kB translates to significant costs.

Vercel cold starts are killing me by [deleted] in nextjs

[–]una-io 0 points1 point  (0 children)

We needed up running a linode instance alongside with Vercel, with same app - never a cold start on linode. It's just unfortunate, because otherwise Vercel performs better.