Master - Slave Replication

    Date: 06/23/05 (Algorithms)    Keywords: no keywords

    Here is my first attempt at a PULL based Master-Slave replication which also allows
    * Lazy Loading
    * Localized Caching
    * DOS prevention (At least limits resource consumption)

    Questions:
    1) Is this design valid and effecient?
    2) Given the problem domain, can anyone propose a non-locking strategy for the Process Fetch Latest ACL List From Master?


    I should have written this in UML, but I like to brainstorm in flowcharts:

    Source: http://www.livejournal.com/community/algorithms/56644.html

« question || Algorithm of the day? »


antivirus | apache | asp | blogging | browser | bugtracking | cms | crm | css | database | ebay | ecommerce | google | hosting | html | java | jsp | linux | microsoft | mysql | offshore | offshoring | oscommerce | php | postgresql | programming | rss | security | seo | shopping | software | spam | spyware | sql | technology | templates | tracker | virus | web | xml | yahoo | home