[erlang-questions] A visual tour of Erlang

Torben Hoffmann <>
Sun Jun 3 07:39:58 CEST 2012


Hi Anoop,

Erlang has its own VM, so all those processes are very lightweight compared to OS processes. 

The basic unit of computation in Erlang is a process with its own memory space and you can only communicate with a process by sending it a message.  

This set-up is necessary if you want to build a fault tolerant system - the last ingredience is the ability to link and monitor processes. Two linked processes will die if either of them dies. A monitor will be notified if the process it monitors die. 

These simple mechanisms is what allows Erlang to work so well. 

Hope this clarifies things a bit for you. 

Cheers,
Torben

Sent from my iPhone

On 03/06/2012, at 06.41, Anoop Thomas Mathew <> wrote:

> Hi All,
> 
> That was a cool video demonstration of erlang processes. Nice work. Kudos to Kresten Krab.
> It aroused a question in me that, isn't erlang creating way too many processes, and why is that so?
> If someone can spread some light into this topic, and give a comprehensive explanation about HOW and WHY, that would be great.
> 
> Thanks,
> Anoop Thomas Mathew
> 
> atm
> ___
> Life is short, Live it hard.
> 
> 
> 
> 
> On 3 June 2012 02:30, Björn-Egil Dahlberg <> wrote:
> 
> 
> 2012/6/2 Lukas Larsson <>
> If you find that useful you might want to checkout
> https://github.com/psyeugenic/fgraph as well.
> 
> After that reminder I felt I had to write a README.
> 
> *commit, push*
> 
> There, I fixed it. 
> 
> On Sat, Jun 2, 2012 at 7:24 PM, Matthew Evans <> wrote:
> > Sorry if this is a repost. This was posted on Reddit. Although it probably
> > doesn't have any "real" uses (yet) I think it's a very nice way to model an
> > Erlang VM and your applications.
> >
> > It got praise from our Java developers when I ran it on our Erlang
> > application at work.
> >
> > Cudos to Kresten Krab for writing this application.
> >
> > https://www.youtube.com/watch?v=lHoWfeNuAN8
> >
> > https://github.com/krestenkrab/erlubi
> >
> >
> >
> > _______________________________________________
> > erlang-questions mailing list
> > 
> > http://erlang.org/mailman/listinfo/erlang-questions
> >
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
> 
> 
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
> 
> 
> _______________________________________________
> erlang-questions mailing list
> 
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20120603/02c38182/attachment.html>


More information about the erlang-questions mailing list