Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Prior to embarking on my quest to develop a database replication mechanism in Perl, I thought I'd tap the collective wisdom of my fellow monks. Basically, I need a reliable and manageable database replication mechanism for implementing a hub-and-spoke topology using merge replication. I'm currently using SQL Sever 2k replication, but find it has some holes and lacks any real management features.
  • The database is temporal in nature, and conflict resolution is not a big issue
  • Typically have about 100 sites (spokes) per hub
  • Data size is about 1MB per replication, sometimes over slow dial-up connections
  • Since opening firewalls requires work, HTTP tunneling might be worth considering
  • Currently all databases are SQL Server 2k, but I will need to include Oracle soon
  • Must be secure
  • Management of the overall replication process is important (IMO as important as the replication mechanism itself)

Due to the temporal nature of the database, it is possible to decouple replication from the database. That is, it would be possible to use a messaging scheme that would replicate the data and have a separate mechanism for handling database loading as well routing messages from the hub to the appropriate spokes.

Any design insights or pointers to useful modules is appreciated.

In reply to DB Merge Replication by trialmonkey

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others wandering the Monastery: (4)
As of 2023-12-04 03:18 GMT
Find Nodes?
    Voting Booth?
    What's your preferred 'use VERSION' for new CPAN modules in 2023?

    Results (20 votes). Check out past polls.