Comments on: Stateless vs stateful web apps

By: Andrew MacKenzie

Andrew MacKenzie — Wed, 10 Feb 2016 09:37:00 +0000

In reply to josevalim. np, the semantics are maybe more noticeable to me because I recently worked in the pay tv space where the distinctions between broadcast, multicast and unicast/stream were quite important ;)

By: josevalim

josevalim — Wed, 10 Feb 2016 08:55:00 +0000

In reply to Andrew MacKenzie. Perfect. I will amend that section, thank you!

By: Andrew MacKenzie

Andrew MacKenzie — Wed, 10 Feb 2016 07:25:00 +0000

When describing the workflows, please note that “broadcast” != “transmit”. The only message that is truly “broadcast” is the one from the pubsub system out to all clients.

By: Renan Ranelli

Renan Ranelli — Thu, 04 Feb 2016 18:20:00 +0000

“Deployment teams need to manage extra tooling, both in terms of storage, web servers and monitoring.”

Its very nice to see such warning. Software engineers often ignore the costs of handling such complex cases in production.

In non-software engineering, if you wan’t some piece of equipment to be reliable you really strive to minimize the number of components. Fire safety equipment is a great example of such cases.

Also, the preempted nature of the Erlang renders the whole “avoid to block the channel” problem inexistent. A process will never hang the whole VM even if it takes 5 minutes to complete its task.