SitePoint Sponsor

User Tag List

Results 1 to 2 of 2
  1. #1
    SitePoint Member
    Join Date
    Dec 2004
    Location
    India
    Posts
    19
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    High availabity and Database Design

    This is one of the questions in my mind for a long time. How do Facebook or any such website/app which has more than a hundred million users maintain there database?

    I believe that everything cannot be put into a single database. If this is the case should there be multiple databases handling different sections? Different sections like: one database for status, one for photographs and one for users…

    Can the database schema be made relational?

    500 million+ users and growing, if average one user has 10 text updates, 5 billion rows (at least), which should be 10% of data that Facebook actually handles.

    I read somewhere that Facebook has 1800+ sql instances out of which 800+ are memcached. Should these DB instances be identical? How might these be designed?

  2. #2
    SitePoint Author silver trophybronze trophy
    wwb_99's Avatar
    Join Date
    May 2003
    Location
    Washington, DC
    Posts
    10,633
    Mentioned
    4 Post(s)
    Tagged
    0 Thread(s)
    Lots of good resources on this all over the place, but the short answer is write-thru memcaches and crazy distributed no-sql databases.


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •