Inside Discord's Massive Message Storage System

[@harrypotil860]

👌 👌 loved the way paused when 4:24 memorable 7:22 Quorum Consistency level 7:55 Data Services 8:19 Tokyo 10:09 RAID 11:41 p99 latency

[@DreamStreet2012]

This content deserves more likes. Keep it up. Cheers from Ukraine!

[@SoftwareDeveloperDiaries]

Thanks my friend, happy to have you here! Love Ukraine with all my heart! ❤️

[@MjCarnaje-jd5ut]

I like this kind of content! Cheers from Philippines!

[@SoftwareDeveloperDiaries]

Wow, Philippines! Happy to hear mate! 😊

[@Y-JA]

Discord could've spared themselves time and money by just using Mysql with Vitess and Rocksdb as the database engine just like Whatsapp and Messenger did.

[@jaysistar2711]

It still seems unclear why MongoDB couldn't do what the other databases are doing. Between capped collections, sharding, and indexing, I'm not sure what specific problem that they had.

[@SoftwareDeveloperDiaries]

Indeed. "because it is complicated to use and not known for stability" is the only thing that they mention when it comes to that.

[@fanciestbanana4653]

MongoDB is generally known to be slower

[@sketchychillandchill]

It's the messier db I ever saw. And slow af

[@jaysistar2711]

​@@fanciestbanana4653That doesn't agree with my observations.

[@jaysistar2711]

​@@sketchychillandchillWith multiple shards and proper indexing, I have found it to be faster than previous solutions in almost every case. There were a few where column stores were better, but access patterns will tell you which storage strategy would work better.