3 ms·
I wonder what the benefits of this approach is to say, a json driven microservice between elixir and ruby?
by mackdaddysly 10y ago
I wonder what the benefits of this approach is to say, a json driven microservice between elixir and ruby?
- davidw 10y agoProbably faster and more direct and less fiddling around with encoding stuff in JSON. I'm pretty sure both Ruby and Erlang have richer types than JSON.
- sjtgraham 10y agoRunning 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 10y agoI hesitate using Erlang/elixir for this than aws lambda + event distribution. Any thoughts?
- vikiomega9 10y agoIsn't aws lambda better suited for short running tasks?
- dfischer 10y agoWhat's a long running task?
- vikiomega9 10y agoI think heuristic is running time of about 5 or 10 minutes.
- abritinthebay 10y agoIf you don't need low latency and are ok with the extra architectural overhead... there's nothing wrong with that. Different use cases
- dfischer 10y agoMany 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 10y agoWell... it's a win for both. It means it's easy to write performant and highly concurrent microservices. Latency is part of that.
- deleted 10y ago[deleted]