Erlang for web-developers

[Dmitrii Dimandt]

I couldn't leave a reply to Yariv's
post<http://yarivsblog.com/articles/2006/08/27/to-web-developers-think-outside-the-thread>because
of some error I kept on receiving, so I decided to respond here.

I think that besides "erlang-telecom-erlang-telecom" web developers should
also be told this:

- Mnesia is a nice database for small amounts of data - 4-8 GB, not more
:))) (am I correct on this estimate?)

- Quite a lot of things can be parallelized in web development. Most
notably, logging and post-process actions:

-- Once you do an action you can spawn a separate logging process and return
to the user immediately
-- Once you accept all data (most notably, image files), you can spawn
separate processes to do whatever with the data at hand (scale, crop,
rotate, move to a different folder etc. etc.) and return to the user
immediately

Many web developers don't even understand that this, indeed, is possible.

I think that in order to sell Erlang to web developers, we need to focus
exactly on the things that can be "branched off". Because telecom stuff is
interesting, but it also is scary. What else can we lure web developers
with?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20060828/6ef6a861/attachment.htm>