Hi Paul!
On 3/23/10 3:24 AM PDT, "Paul McCullagh" <[email protected]> wrote: > Hi Robert, > > On Mar 22, 2010, at 8:43 PM, Robert Hodges wrote: > >> >> 1.) What are the "big" problems in replication? Let's say we have >> things >> like availability and basic read scaling basically handled. What's >> next on >> the list? (Big data, No-SQL, replication/database impedance >> mismatch due to >> faster hardware, complex topologies, management, etc., all >> suggestions are >> welcome.) >> >> 2.) What replication solutions are emerging to address those >> problems? Jay >> and I work on or know most of the usual suspects like Drizzle, >> Tungsten, >> Galera, MySQL 5.4, Rabbit MQ, etc. However, if there's something >> really >> cool out there we'll add it to the list. > > <plug> > It may be relevant to mention engine-level replication in a survey of > the replication landscape. This is now built into PBXT. > > Engine-level replication is not as flexible as Drizzle replication, > for example, but it is extremely efficient. > > It is relatively low-level, but not as low level has block device > replication (DRBD), and is much easier to setup and maintain. > > I believe this has a role to play in its position between the block- > level replication and the high-level, replicate to anywhere, being > developed for Drizzle, and global replication systems like Tungsten. > </plug> > This is a very interesting point. Physical and logical replication are kind of like Yin and Yang for building systems. I was thinking of pointing out in the talk the work going on in PostgreSQL with PG 9 and streaming replication/hot standby. The PostgreSQL approach, as you are probably aware, has been to implement very solid physical replication while leaving logical replication to external, trigger-based products like Londiste. How do you get around some of the issues like snapshot maintenance for queries that are currently consuming cycles in the PostgreSQL effort? In the current PG 9 alpha users may have to choose between between up to date slaves and ability to run queries that maintain a snapshot for a lengthy period of time. Meanwhile, it sounds like time to look carefully at what you have done with PBXT. Cheers, Robert _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
