News for hackers. Stuff that matters.

A comment on Erlang's not about lightweight processes and message passing. Parent comment

Re:Erlang's not about lightweight processes and message passing by Thaxll on Friday January 27, 2023 @01:13PM (#34549577)
Except you still need to run and deploy your Erlang app somewhere which might end up on Kubernetes.

Kubernetes is just better than Erlang for process managment because it does more and is completely language agnostic, imagine you can't build some part of your system in Erlang but you need the same kind of functionality what do you do?

[ Parent | on HN ]
Re:Erlang's not about lightweight processes and message passing by calo_star on Saturday January 28, 2023 @01:29AM (#34555707)
Depending on the size of your component that can't be built in Erlang, you may be able to use NIF and throw it on the dirty scheduler.
[ Parent | on HN ]
Re:Erlang's not about lightweight processes and message passing by mapcars on Monday January 30, 2023 @06:09AM (#34578267)
You can make NIF, you can implement Erlang protocol to talk to the node (and I have done it). Both of those are possible but does it worth it in the end? Is it worth to have orchestration builtin into the language and locked with some particular features instead of a full-fledged devops setup? The only argument I have is in early stages of development it might save some time.
[ Parent | on HN ]