We went through a similar decision making process when considering how to build RabbitMQ. As explained in our FAQ, there are several reasons why Erlang/OTP has out of the box features suitable to building an enterprise grade (and indeed, 'carrier grade') messaging system.
The technologies that the Hypernumbers guys compared Erlang/OTP with, are designed for non-event-driven stacks. Why would you use an architecture for building database backed web sites, when building a messaging system?
So, we came to more or less the same conclusion :-)
I'd be interested in how people are getting on with cases where they are using an actors based approach for 'simple' web sites. Not just using Erlang/OTP, but also Scala/Lift.
Geek and freelance web developer. Other interests: Photography, running, drinking coffee and foreign languages (Portuguese, Italian, French and Spanish. German is my native language).
Hire me
as Javascript Expert. I have experience with many of the common client and server-side web technologies. My current focus is development of web apps optimized for the iPhone. Remote or on-site. Contact me to check for availability and rates.
2 comments:
We went through a similar decision making process when considering how to build RabbitMQ. As explained in our FAQ, there are several reasons why Erlang/OTP has out of the box features suitable to building an enterprise grade (and indeed, 'carrier grade') messaging system.
The technologies that the Hypernumbers guys compared Erlang/OTP with, are designed for non-event-driven stacks. Why would you use an architecture for building database backed web sites, when building a messaging system?
So, we came to more or less the same conclusion :-)
I'd be interested in how people are getting on with cases where they are using an actors based approach for 'simple' web sites. Not just using Erlang/OTP, but also Scala/Lift.
Thanks for the link! Best regards from a recent Erlang fan, born in Argentina :) and living in Switzerland (Lausanne). Cheers!
Post a Comment