This link has been bookmarked by 27 people . It was first bookmarked on 03 Aug 2006, by Matt McAlister.
-
26 Mar 08
-
21 Mar 08
-
09 Aug 07
-
29 Jul 07
-
From my end, the worst MySQL moment was when, in the midst of a colo move we decided that we could bring the system back up before we had moved our slave database. After all, what are the odds of the primary going down in the 2 hours it would take to schlep the slave over and bring it up? Apparently the odds were 100%.
-
Like everybody else, we started with One Database All Hail The Central Database, and have subsequently been forced into clustering. However, we've eschewed any of the general purpose cluster technologies (mysql cluster, various replication schemes) in favor of explicit data partitioning. So, we still have a central db that keeps track of where to find what data (per-user, for instance), and N additional dbs that do the heavy lifting. Our feeling is that this is ultimately far more scalable than black-box clustering. Right now we're still in the transition process, so we remain vulnerable to overload. As Cory mentioned, we're moving to an HTTP-based internal communication model in order to improve our flexibility.
-
-
27 Jul 07
-
18 May 07
-
24 Mar 07
-
14 Mar 07
-
05 Nov 06
-
25 Oct 06
-
16 Sep 06
-
04 Aug 06
-
24 Jun 06
-
08 Jun 06
-
21 May 06
-
16 May 06
-
03 May 06
-
28 Apr 06
Page Comments
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.