[url00]

The reality is modern Kubernetes infrastructure looks a lot like BEAM, at least in the capabilities it offers. That's the far more common way of deploying highly scalable, self-healing systems in the current year. Plus, with k8s you're not constricted to a single language (there are a few more than Erlang/Elixir, but nothing popular) with limited developer resources and interest.

[MarceColl]

So now you need several servers, an orchestrator, tons of YAML, arcane and terrible error messages and a devops team to kind of match the BEAM? That's... not a good look

[AlchemistCamp]

Yes. This is a big part of what initially drew me to Elixir. It's more than feasible to run a server on a cheap VPS, get great, though not quite Golang or low-level language performance and have a much easier scaling story when you need multiple machines.

More importantly, you generally don't need an external queue service, in-memory KV store, task scheduler or many of the other things that JS/Ruby/Python stacks need. By consolidating just about everything but the DB in a single, well designed system, it's possible for a very small team to take on relatively large challenges on a smaller budget.

[da02]

Which VPS providers do you recommend? Which relational databases do you use with Elixir?

[MarceColl]

I use a dedicated hetzner server (12 cores 64gb ram) for 60 euros with postgres

[Cyph0n]

Not an Elixir expert, but my impression is that Postgres is a common choice. It’s well supported by both Ecto (ORM) and Oban (job queue).

[Thaxll]

Where does your Erlang code runs in the first place? ( maybe kubernetes already )

Kubernetes does all of that in a standard and easy way but also is completely language agnostic. So your Python code without modidication can benefit from it.

[MarceColl]

in my case it runs on a good old server.

> So your Python code without modidication can benefit from it.

that's not completely true though, say you have two python processes, you need to solve yourself how they communicate, HTTP? a message broker? through the DB? You need to handle errors, stateful deployments.

You can deploy python code without modification if the python code does very simple things. My point is that the BEAM gives you a lot of this mostly presolved for you without having to add more infrastructure.

[tough]

is that a fair comparison? i dont love k8s but you can deploy anything to it, not just erlang or elixir

[toast0]

You can use a BEAM system to orchestrate other code, too. As ports, port drivers, nifs, c-nodes, just other OS processes spawned and using IPC/sockets. Lots of options. Using Erlang to supervise an OS process doing work perhaps enhances the isolation principles of BEAM.

[tough]

oh interesting wasnt really aware

so you could use beam to orchestrate go or rust services communicating over IPC? Nice

[rramadass]

See also CloudI a Cloud System built using Erlang - https://cloudi.org/index.html

[tough]

TY! Very interesting!

[giraffe_lady]

It's snarky but I think it is a fair comparison. You do have extra capabilities over what BEAM offers, in exchange for having to manually handle a lot of things BEAM either handles invisibly or at least comes with usable defaults for.