[erlang-questions] More benefit and practical example of distributed Erlang/OTP (simple) application

Tristan Sloughter t@REDACTED
Mon Aug 12 17:59:25 CEST 2019

> If i try to compare what i learn in https://learnyousomeerlang.com/distributed-otp-applications with my experiences, i can't see the benefits of distributed erlang/otp app that explained in the book. 

And you are probably right.

There is an important note in that chapter:

> *Note:* In terms of distributed programming fallacies, distributed OTP applications assume that when there is a failure, it is likely due to a hardware failure, and not a netsplit. If you deem netsplits more likely than hardware failures, then you have to be aware of the possibility that the application is running both as a backup and main one, and that funny things could happen when the network issue is resolved. Maybe distributed OTP applications aren't the right mechanism for you in these cases.

If you have a service that, for whatever reason (like not being a stateless service), you only can have 1 instance active at a time but you have additional nodes you can use as backups in case of hardware failure on the current active node then distributed applications are an answer.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20190812/a7511ab1/attachment.htm>

More information about the erlang-questions mailing list