-----Original Message----- From: Richard Reina [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 07, 2004 11:30 AM To: [EMAIL PROTECTED] Subject: When to cluster vs. replicate
For some time I have been considering replication for added redundancy so that should something happen to the server I could quickly deploy the slave as the main server until the problem is fixed. However, now I reading about great MySQL clustering is. What exactly is clustering and should I look to employ it instead of replication? Clustering is designed for real-time redundancy of a transaction. Replication is batch redundancy system that works on top of any mySQL storage engine. Use Clustering if you need to provide multiple write points and your system needs to stay alive in the event of a single server crashing. Use Replication if you want semi-realtime backup or need to use a storage engine that is incredibly fast like myISAM to spread out database READ access load. Replication currently doesn't allow a SLAVE to have multiple MASTERS, thus it cannot be used out of the box as a "clustered solution". -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
