-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/01/07 08:12, chris smith wrote: >> Ever read anything on how myspace is laid out? The big ones need >> replication to handle the traffic. > > Actually no. > > http://highscalability.com/livejournal-architecture > > "Using MySQL replication only takes you so far." (Yeh it's mysql but > the point is valid regardless). > "You can't keep adding read slaves and scale." > > A lot use sharding now to keep scaling (limiting to "X" users/accounts > per database system and just keep adding more database servers for the > next "X" accounts). Hmmm. Horizontally partitioning your "database" into multiple physical databases is 10+ years old. At least. This is how DEC implemented the billing database for DirecTV, and how we implemented *large* toll systems in the US Northeast. In addition to the account databases, you need a "reference" database for tables that can't be partitioned by account, be able to run queries across databases, and middleware that knows how to direct transactions to the correct database. - -- Ron Johnson, Jr. Jefferson LA USA Give a man a fish, and he eats for a day. Hit him with a fish, and he goes away for good! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG2c6QS9HxQb37XmcRAkuGAJ4thc+owEX8OJl1qaTrY+krHkMIwgCfWver aUEiSPkrw4Gnf7dI0ftSVJ0= =4wFD -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
