Исправление loz, (текущая версия) :
Вот ответ на этот самый вопрос от создателя Эрланга: http://erlang.org/pipermail/erlang-questions/2017-October/093931.html
TLDR:
Hard real time: All requests MUST be satisfied within a specified time. Note this does not mean fast
Soft real time: Some requests might miss the deadlines
This is what Erlang was designed for - hundreds of thousands of processes that are largely inactive - then they wake up and request a small amount of computation. The odd process might request a large amount of processing but this should not block the other processes.
Исходная версия loz, :
Вот ответ на этот самый вопрос от создателя Эрланга: http://erlang.org/pipermail/erlang-questions/2017-October/093931.html
TLDR:
Hard real time: All requests MUST be satisfied within a specified time.
Note this does not mean fast
Soft real time: Some requests might miss the deadlines
This is what Erlang was designed for - hundreds of thousands of processes that are largely inactive - then they wake up and request a small amount of computation. The odd process might request a large amount of processing but this should not block the other processes.