News for hackers. Stuff that matters.
Re:You don't need Next.js – Why we migrated from Next to React by dartos on Wednesday January 01, 2025 @02:15PM (#42568427)
It’s not necessarily that it’s hard, but to be effective with kubernetes you need to understand a lot of infrastructure concepts like DNS, load balancing strategies, docker, storage drivers, service discovery, what exactly a pod is, what exactly a container is, etc.

It’s a lot of up front knowledge needed for marginal benefit at small to mid scales.

There’s a lot of steps if the “write your deployment yaml” step.

Re:You don't need Next.js – Why we migrated from Next to React by merb on Wednesday January 01, 2025 @02:20PM (#42568477)
If you are small or mid scale and you need lots of compute between 8 5 to 8 on Monday till Friday it basically the best thing you can you to schedule your workload.

If you need some things like load balancing and zero downtime deploys etc you probably will build your own k8s which is often worse

Re:You don't need Next.js – Why we migrated from Next to React by dartos on Wednesday January 01, 2025 @11:26PM (#42571633)
Or you can deploy on app engine, lambda, firebase, etc.

Kubernetes is not the only game in town.

Sometimes shipping asap is more important. As with just about anything in tech, it’s about tradeoffs.

I may be biased, since I worked in devops before k8s came out, but building a decently scalable system architecture with load balancing and rolling deployments is pretty straightforward with monolithic systems. Especially since service discovery isn’t really a concern. Horizontal scaling works well in many many cases.

Realistically any app simple enough to be deployed by hand with a few docker containers will not be difficult to convert to k8s anyway.

Re:You don't need Next.js – Why we migrated from Next to React by echelon on Wednesday January 01, 2025 @02:19PM (#42568459)
You're doing the moral equivalent of that when you're setting up on bare metal.