[erlang-questions] How would you architecture a ...
Mon May 11 08:08:00 CEST 2009
What are you planning on storing with mnesia? I would be very careful about
it, because it's not all roses. First of all mnesia is very inflexible if
you wish to change your data schema, pretty damn slow if you use
transactions and I've had situations where I lost the database completely.
Mnesia is very unsuitable as a website DB.
One of the biggest design mistakes I made a 1.5 years ago, for the server I
am still developing is relying too heavily on mnesia. When you're starting
out in Erlang, mnesia seems great, but with time you realise that it's way
more truble than it's worth.
On Sun, May 10, 2009 at 11:13 PM, Mark Selby <> wrote:
> ... web server which allows different hostnames to have their own mnesia
> I've been looking at Yaws because I can use erlyweb and erlydb to an
> The idea of using an Erlang "node" for each hostname seems the favourite
> at the moment as that allows "nodes" to have their own Mnesia schema (I
> think and hope), and other machines can be added, probably ultimately
> leading to the original yaws server becoming a request proxy to the
> different "servers" which are doing the grunt.
> So that leads to a front end which is just doing a lookup on hostname
> and passing the request on to the appropriate "node", and relaying
> whatever it gets back to the client.
> There are only three "controllers" that my app needs, and none are that
> complicated. Appmods or Controllers?
> How do I keep a connection open in Yaws to minimize response times? For
> example, to a remote imap server?
> I'm so impressed with Erlang and Mnesia. I knew there was a reason to
> learn C and assembler all those moons ago! They make Erlang seem more
> familiar than anything else I've used.
> Thanks, btw, for any helpful thoughts.
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions