[erlang-questions] Can Mnesia replace conventional RDBMS?

Rapsey rapsey@REDACTED
Sun Jun 2 10:50:06 CEST 2013

I believe it's 4gb per fragment. Mnesia sounds great at first, but it
has some difficult operational issues. The biggest one is records.
Once you set your schema, it will be extremely challenging to change.
Records are inflexible. So if you need to change your schema, you need
to change your record definition. If  you change your record
definition, the database and your code needs to be updated at the same
time. I don't see how that is possible without taking your entire
service offline.


On Sun, Jun 2, 2013 at 10:19 AM, Yash Ganthe <yashgt@REDACTED> wrote:
> The Mnesia documentation says:
> largest possible mnesia table (for now) is 4Gb
> A table can be distributed across nodes so that part of it remains on one
> node and part on another. In a distributed sense, does this mean 4GB per
> table per node, or 4GB per table across nodes?
> Is there a way by which Mnesia can be used in a system that will store about
> 100GB of data in some tables and support ACID properties just like popular
> RDBMS's like MySQL/Oracle?
> Thanks,
> Yash
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions

More information about the erlang-questions mailing list