[erlang-questions] how to scale into the cloud using process? example computing simple average
Torben Hoffmann
torben.lehoff@REDACTED
Tue May 26 09:27:57 CEST 2009
I think you are taking a too big bite to start with, but it is good that
your interest is driven by a concrete need and not just technology frenzy!
http://heroku.com/ uses Erlang for their routing mesh.
http://www.infoq.com/news/2008/06/introducing-vertebra is built with Erlang
+ Ruby.
As Bengt said: get a book and then go to one of the Erlang Factory
conferences - or have a look at the presentations from the previous ones.
That should give you some ideas on how to proceed.
Cheers,
Torben
On Tue, May 26, 2009 at 8:01 AM, Kid Erlang <kiderlang@REDACTED> wrote:
> On Tue, May 19, 2009 at 2:26 AM, Bengt Kleberg <bengt.kleberg@REDACTED
> > wrote:
>
>> The return value of spawn/1 is the (Erlang) process identity. If you
>> want data from a process you have to send it (using !) and receive it
>> (using receive).
>>
>
> okay I have rewrite my project to use receive with spawn, but I still do
> not get how to handle errors? especially in the cloud?
>
>
>> It would be a good idea to read one of the Erlang books or the online
>> documentation.
>>
>
> what book is best for me to read? and I cannot find online documentation
> for how to use spawn + receive + messages to scale into the cloud?
>
> that is my main worry: say I have something that uses spawn + receive +
> messages. how do I make it scale into the cloud? where can I find online
> documentation on this? i want my erlang program to run on as many systems
> as I need it to for however many users. how do I do that?
>
> - Kid Erlang
>
>
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20090526/2f0cce83/attachment.htm>
More information about the erlang-questions
mailing list