You&#x27;re underestimating the difficulty of scaling Mnesia the way WhatsApp did (one source says &quot;In-memory Mnesia database using about 2TB of RAM sharded across 16 partitions to store about 18 billion records.&quot; [1]). The prevailing wisdom in the Erlang community was that Mnesia could not be made to do such things. The only well-known user of Mnesia at anywhere near this scale prior to WhatsApp was Klarna. To achieve this, Klarna employed at least one of the original Mnesia developers who wrote proprietary patches for their system [2]. So while you accuse parent of being reductionist, your views of WhatsApp&#x27;s engineering challenges also seem reductionist. Erlang&#x2F;OTP software doesn&#x27;t write and scale itself ... large-scale distributed systems are decidedly non-trivial no matter what tools you&#x27;ve chosen.<p>[1] <a href="http:&#x2F;&#x2F;highscalability.com&#x2F;blog&#x2F;2014&#x2F;3&#x2F;31&#x2F;how-whatsapp-grew-to-nearly-500-million-users-11000-cores-an.html" rel="nofollow">http:&#x2F;&#x2F;highscalability.com&#x2F;blog&#x2F;2014&#x2F;3&#x2F;31&#x2F;how-whatsapp-grew-...</a><p>[2] <a href="https:&#x2F;&#x2F;www.erlang-factory.com&#x2F;upload&#x2F;presentations&#x2F;601&#x2F;EUC2012-009.pdf" rel="nofollow">https:&#x2F;&#x2F;www.erlang-factory.com&#x2F;upload&#x2F;presentations&#x2F;601&#x2F;EUC2...</a>