On Wed, Nov 19, 2003 at 10:36:43AM +1300, Mark Mackay - Orcon wrote: > Clustered databases > ------------------- > Oracle or some database with multiple write masters and cluser-wide locking > for writes springs to mind. I understand there is problems with MySQL > one-way replication and directing all writes to a master server, but reads > from multiple slaves - due to write-locking not being supported thus the > slave getting out of sync with the master, etc. I scanned the list again > recently but couldn't find any obvious posts with solutions for this. > > Last minute addition >> I notice SAP DB is now MySQL MaxDB and is available. > Anyone looked at this as a viable backend for dbmail? Can't for the life of > me find the details on replication support/etc on the site... I don't think MaxDB supports multiple masters. It offers some features that would be nice though, like hot backups and automatic failover. The MySQL Proxy should make using MaxDB with dbmail easier. > Partitioned databases > --------------------- > The old customea A-E on database server 1, F-L on database server 2, etc. > This would seem to do the trick, although with dbmail it may be user_idnr > 1-50,000 on DB1, 50,001-100,000 on DB2 I guess, with some sort of central > mailbox -> store index table. I haven't looked at the code for 2.0 recently, > but from memory 1.x maintained a persistent connection with the mailstore, > thus this could be quite bad if there were say 100 database servers. I'm not > sure what the overhead would be for connection setup/teardown if doing > dynamic connections to different servers.
You could have POP/IMAP servers dedicated to each db server and use perdition to proxy to the appropriate cluster. Likewise, you could have your MTA lookup which database to deliver to and forward messages to a set of smtp servers dedicated to each database server or modify dbmail-smtp to support multiple database servers. xn
