Use one big server

Re:Use one big server by dugmartin on Tuesday August 02, 2022 @11:30AM (#32319862)

I think Elixir/Erlang is uniquely positioned to get more traction in the inevitable microservice/kubernetes backlash and the return to single server deploys (with a hot backup). Not only does it usually sip server resources but it also scales naturally as more cores/threads are available on a server.

[ Parent | on HN ]

Re:Use one big server by lliamander on Tuesday August 02, 2022 @12:50PM (#32321138)

Going from an Erlang "monolith" to a java/k8s cluster, I was amazed at how much more work it is takes to build a "modern" microservice. Erlang still feels like the future to me.

[ Parent | on HN ]

Re:Use one big server by dougmoscrop on Tuesday August 02, 2022 @03:07PM (#32322952)

Can you imagine if even a fraction of the effort poured in to k8s tooling had gone in to the Erlang/OTP ecosystem instead?

[ Parent | on HN ]

Re:Use one big server by dboreham on Tuesday August 02, 2022 @11:33AM (#32319930)

This is the norm. It's only weird things like Node.js and Ruby that don't have this property.

[ Parent | on HN ]

Re:Use one big server by hunterloftis on Tuesday August 02, 2022 @12:30PM (#32320848)

While individual Node.js processes are single-threaded, Node.js includes a standard API that distributes its load across multiple processes, and therefor cores.

- https://nodejs.org/api/cluster.html#cluster

[ Parent | on HN ]