Database Replication OOD Pattern

Posted by MrOnigiri on Stack Overflow See other posts from Stack Overflow or by MrOnigiri
Published on 2009-08-21T11:54:03Z Indexed on 2010/05/12 8:44 UTC
Read the original article Hit count: 354

Greetings fellow overflowers,

After reading on MSDN about correct strategies on how to perform database replication, and understanding their suggestion on Master-Subordinate Incremental Replication. It left me wondering, what OOD design pattern should I use on this...

The main elements of this strategy are the Acquirer, the Manipulator and the Writer. The first fetches data from the database and passes on to the second which might perform simple transformations to the data, before handling it to the final element, the writer, that writes the desired data on the destination Database.

I thought about using the Chain of Responsibility pattern, but the Acquirer, Manipulator and Writer don't share a common role among theme, so It makes no sense.

Should these elements be written as separate classes, or methods inside my service? Of course I'll be creating a DB Helper class as well, but that doesn't constitutes a problem.

Wondering what your opinions on this are! Thanks for your replies

© Stack Overflow or respective owner

Related posts about database

Related posts about replication