Hi Jeremy, Thanks!! I'm writing a multi-threaded design for Tungsten that replicates shards in parallel-we are working with a lot of customers like SaaS businesses for whom the causal independence between shards is trivial to assert. This design will also work on Drizzle.
What kind of extra information did the Google hack add? I don't think I saw that one. Cheers, Robert On 3/22/10 7:52 PM PDT, "Jeremy Zawodny" <[email protected]> wrote: Robert... On Mon, Mar 22, 2010 at 12:43 PM, Robert Hodges <[email protected]> wrote: Hi All, 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.) Latency. Specifically I want muli-threaded replication so I can better take advantage of mutli-core slaves. I'm willing to assume the "risk" associated with saying "yes, I'm sure that each of these logical dbs are logically separate, and no statements will cross them." Cache consistency and invalidation. Google had a nice hack for stuffing extra info into the binlog so that other tools could pick up the changes and export them into non-MySQL systems. Jeremy
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
