It also came about before CAP was postulated, and does nothing to automatically resolve partitions. It doesn&#x27;t -die-, but it was clearly built with a &quot;we&#x27;ll run this in our own data center&quot; mentality. In the event of a partition, it goes immediately to split brain mode, which each side of the partition running separately, allowing both writes and reads, and doing nothing to try and automatically heal the partition, even if your Erlang nodes reconnect.<p>This isn&#x27;t necessarily a bad thing; it&#x27;s a very easy model to reason about, it rarely has an issue if your cluster doesn&#x27;t span more than one data center, and it lets you know when it happens via events you can subscribe to. But doing anything different, up to and including healing the partition automatically, is left to the user.<p>There&#x27;s also a few warts due to its history; disc only tables have a rather small max size (so if you&#x27;re not expecting everything to be stored in RAM as well, you don&#x27;t want to use Mnesia), indexes are shockingly inefficient for writes, and a few other odds and ends that I don&#x27;t really remember. For persisted, but fast, storage in Erlang, where partitions aren&#x27;t common, it&#x27;s great, but outside of those sorts of use cases there&#x27;s probably something better.