Migrating Messenger storage to optimize performance

They say that they brought some new search features to mobile, though I would prefer if they fixed their search on desktop (or in general) first, as it only returns results from recent messages.<p>Until sometime in 2016&#x2F;2017 it was possible to look for specific things at whatever time (e.g. 2011) and now even things from &lt;3y ago don&#x27;t return anything.

Whatever you may think of social networking, Facebook takes huge amount of pains to ensure reliability. They moved all the data from spinning disks to flash, also migrating to a new db. No downtime at all.<p>I&#x27;m a bit unclear as to how this process resulted in 90% decreased storage use.

Facebook has been using RocksDB more and more (now messenger, but also Instragram’s flavor of Cassandra). I wonder if Google has a similar penetration of LevelDB (and we just don’t hear about it because Google’s infrastructure work isn’t open source)

During the dual-write phase, what happens if one request succeeds while the other doesn&#x27;t?

What about giving me an easy option to export my messages while you are at it?

TL;DR - Moved from HBase to MyRocks engine on MySQL sitting on top of NVMe storage via their Lightning Server [1], which is a JBOF (just a bunch of flash) setup using x16 PCIe.<p>[1] <a href="https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;989638804458007&#x2F;introducing-lightning-a-flexible-nvme-jbof&#x2F;" rel="nofollow">https:&#x2F;&#x2F;code.facebook.com&#x2F;posts&#x2F;989638804458007&#x2F;introducing-...</a>

Great, now they can serve video ads in Messenger more easily.