I worked in a company that did this, because of the slightly different business requirements they had regarding "publishing" on demand. Needless to say, it didnt end well.
Reinventing replication is usually a sign of poor application architecture; change the code, not the concept of replication.
Comments
Um... you just "reinvented" replication.
I worked in a company that did this, because of the slightly different business requirements they had regarding "publishing" on demand. Needless to say, it didnt end well.
Reinventing replication is usually a sign of poor application architecture; change the code, not the concept of replication.
Does the same sentiment hold for a heterogenous set of databases? e.g. Microsoft SQL Server <-> WebSQL