3 ms·

Facebook uses MySQL as a glorified key-value store, not as a traditional RDBMS.

• spudlyo 14y ago
  So I voted you down because you're wrong. http://www.youtube.com/watch?v=Zofzid6xIZ4#t=04m10s http://www.youtube.com/watch?v=Zofzid6xIZ4#t=04m10s Click on that link and listen to Mark Callaghan, an engineer at Facebook, talk about their query workload. From a slide: The Workload - OLTP - Fast Queries - Simple Joins - Fast Transactions - Secondary indexes critical to performance - Some rows very hot
  • brown9-2 14y ago
    Thanks for the link, the video looks interesting. I was basing my claims on this talk (also from 2010) http://www.infoq.com/presentations/Scale-at-Facebook http://www.infoq.com/presentations/Scale-at-Facebook. Or it might have been this other talk: http://www.infoq.com/presentations/Facebook-Software-Stack http://www.infoq.com/presentations/Facebook-Software-Stack
    • spudlyo 14y ago
      That's really interesting. The two folks from Facebook contradict each other when talking about joins. Aditya says "No joins in production.", while Mark says "Some of the stories I read about sharded SQL state that you don't do joins when you have sharded MySQL, and that has never been the case for the workloads that I watch. You're always doing some complex query processing within a shard." Anyway, I can see how you might have come away with the notion that MySQL is a glorified key value store by watching the first video which only briefly touches on their MySQL usage.