The first is a storage limitation of 2 Giga bytes per file.

The second is that it requires a VALIDATION and fix up cycle after a crash or power failure, so even if the size limitation is lifted, the fix up time on large files is prohibitive.

Mnesia replication is suitable for clustering, but not disconnected, distributed edits. Most of the “cool” features of Mnesia aren’t REALLY useful for COUCHDB.

Also Mnesia isn’t really a general-purpose, large scale database. It works best as a configuration type database, the type where the data isn’t central to the function of the application, but is necessary for the normal operation of it. Think THINGS like network routers, HTTP proxies and LDAP directories, things that need to be updated, configured and reconfigured OFTEN, but that configuration data is rarely very large.

The first is a storage limitation of 2 Giga bytes per file.

The second is that it requires a validation and fix up cycle after a crash or power failure, so even if the size limitation is lifted, the fix up time on large files is prohibitive.

Mnesia replication is suitable for clustering, but not disconnected, distributed edits. Most of the “cool” features of Mnesia aren’t really useful for CouchDB.

Also Mnesia isn’t really a general-purpose, large scale database. It works best as a configuration type database, the type where the data isn’t central to the function of the application, but is necessary for the normal operation of it. Think things like network routers, HTTP proxies and LDAP directories, things that need to be updated, configured and reconfigured often, but that configuration data is rarely very large.