High Scalability - High Scalability - Why are Facebook, Digg, and Twitter so h... - The Diigo Meta page

• 25 Nov 09
  

  luke chi
• 18 Nov 09
  

  scitlec

  !!!

• 02 Nov 09
  

  maristo

  graph database

• 16 Oct 09
  

  Mattia Quilici

  Scalabilità tecnica dei social network

  scalabilità tecnica web

• 14 Oct 09
  

  Martin Weigert

  scaling skalieren social networks facebook digg twitter website yahoo zugriffe

• 

  gustavohartmann

  scalability performance facebook

  • Real-time social graphs (connectivity between people, places, and things).

  • Traditional websites are easier to scale than social networking sites for two reasons:

    
    
    • They usually access only their own data and common cached data.
    • Only 1-2% of users are active on the site at one time.
  • 1 more annotations...

  • • ow think what happens on Facebook. Let's say you have 200 friends. When you hit your Facebook account it has to go gather the status of all 200 of your friends at the same time so you can see what's new for them. That means 200 requests need to go out simultaneously, the replies need to be merged together, other services need to be contacted to get more details, and all this needs to be munged together and sent through PHP and a web server so you see your Facebook page in a reasonable amount of time. Oh my.

      
      

      There are several implications here, especially given that on social networking sites a high percentage of users are on the system at one time (that's the social part, people hang around):

      
      
      • All data is active all the time. 
      • It's hard to partition this sort of system because everyone is connected. 
      • Everything must be kept in RAM cache so that the data can be accessed as fast as possible.
• 

  fulvius longhi

  scalability web2.0 strategy

  • Their caching tier services 120 million queries every second and it's the core of the site.
  • Should permission be consulted when data is produced or consumed, for example? Or what if the data is deleted after it has already been copied around?
  • 1 more annotations...
  • • While all these consistency and duplications problems are interesting, Push on Change seems the more scalable approach for really large numbers of followers. It does take a lot of work to push all the changes around, but that can be handled by a job queuing system so the work is distributed across a cluster.
• 13 Oct 09
  

  barb dybwad

  "Real-time social graphs (connectivity between people, places, and things). That's why scaling Facebook is hard says Jeff Rothschild, Vice President of Technology at Facebook. Social networking sites like Facebook, Digg, and Twitter are simply harder than traditional websites to scale. Why is that? Why would social networking sites be any more difficult to scale than traditional web sites? Let's find out."

  scaling developer social graphs facebook twitter digg social networking

• 

  Damon Snyder

  scalability nosql

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.