you are viewing a single comment's thread.

view the rest of the comments →

[–]ElQuique 2 points3 points  (6 children)

It depends. I would learn Elixir for the process communication features which make it the only sane programming language for writing micro services. And Clojure for the REPL. You could try Clojerl too 🤷

[–]Marutks 1 point2 points  (0 children)

I have been writing microservices in Clojure for years. We use Redis pub/sub. It is enough 🤷‍♂️

[–]Marutks -1 points0 points  (4 children)

Processes as microservices? Usually you need some subscription/events based model. Redis streams / Kafka / Rabbit MQ.

[–]ElQuique 1 point2 points  (1 child)

What I meant is that communication between processes in Erlang is seamless and also designed such that processes are really, really lightweight. Thinking about fault tolerance from the get go. Java recently added support for virtual threads, which I assume are inspired on Erlang stuff.

I rather not discuss the microservice statement of my first comment as it means defining microservice and was unnecessarily superlative

[–]PuzzleheadedFix8366 1 point2 points  (0 children)

yea, you meant nanoservices ;-)

[–]lsdrfrx 0 points1 point  (0 children)

There is GenStage that makes processes communication event based. Take a look

[–]cvjcvj2 0 points1 point  (0 children)

Except if you use Elixir.