[sjtgraham]

Running your applications in Erlang is its own microservices architecture. Each process is essentially microservice that can interact with others on any node in your cluster by sending messages. Everything is handled for your by the runtime. Processes on a different node? No problem, they're easy to discover and if a message does go to another node the serialization is handled for you. Erlang is so powerful I'd actually invert your question.

[dfischer]

I hesitate using Erlang/elixir for this than aws lambda + event distribution. Any thoughts?

[abritinthebay]

If you don't need low latency and are ok with the extra architectural overhead... there's nothing wrong with that.

Different use cases

[dfischer]

Many are preaching erlang/elixir on the OTP/microservice alternative paradigm – that doesn't seem as attractive as the low latency resiliency.

At least to me, as a story.

[abritinthebay]

Well... it's a win for both. It means it's easy to write performant and highly concurrent microservices.

Latency is part of that.

[vikiomega9]

Isn't aws lambda better suited for short running tasks?

[dfischer]

What's a long running task?

[vikiomega9]

I think heuristic is running time of about 5 or 10 minutes.