3 ms·
> But wouldn't it be cool if there were a framework where the developer didn't have to demarcate where services started and ended? Erlang/Elixir, for JVM Akka,
by slver 5y ago
> But wouldn't it be cool if there were a framework where the developer didn't have to demarcate where services started and ended?
Erlang/Elixir, for JVM Akka, for .NET Akka.NET.
- jerf 5y agoNo, it's a bit of a myth that those techs just magically scale everything. They don't make that problem go away at all. You still need to find homes for the services to run on. It does make it a single function call to potentially start up a new service on a remote node, but if you need to be careful about resource use you're hardly any better off than you are with anything else. In a way that can end up being too easy to just add work to systems rather willy-nilly, the ceremony in kubernetes or any other more explicit system can be a good thing.
- slver 5y agoThe question wasn't "how to magically scale everything". The question was why not eliminate the difference between in-process async call and a service, and that's basically what Erlang and actors do.