[erlang-questions] Twoorl: an open source Twitter clone

[Steve]

On May 31, 5:04 pm, "Yariv Sadan" <yarivsa...@REDACTED> wrote:
> ...but it's the only way you can scale this kind of service when N is
> big.

Hmmm, Yariv, aren't you still thinking about this in the way that Dave
Smith pointed to as the heart of the issue? i.e.
Dave said: "My understanding is that the reason they have such poor
uptime is due to the fact that they modeled the problem as a web-app
instead of a messaging system."

I'm aware that you are likely a good way away from hitting any
scalability problems, but some kind of tiering would seem to be
appropriate if twoorl is to be "twitter done right". Yaws at the front
end, definitely - but rather /RabbitMQ/ at the back end. I believe
that you'd then have the flexibility to distribute/cluster as
necessary to scale to the required level (whatever that may be).

For sure, Twoorl is a great demo of what can be done with Erlang in an
incredibly short time. I'm a relative noob to Erlang, and have learned
a great deal from your blog/code/examples.

Steve