[Dbix-class] RFC: DBIx::Class::Storage::DBI::mysql_repl - replicated MySQL data source

[Lee Standen]

How does it handle replication lag?

I don't know if this happens in MySQL, but with DB2 replication, there 
is the potential for data being read to be 15 or more minutes out of 
sync with the "real" data on the master database.  If this happens on 
MySQL as well, then there would be a necessity to query the row(s) you 
plan to update from the master database first, and then throw an 
exception if the data is different.

Normally, due to this possibility, we make all read applications (like 
reports) read from the replica database, and all applications which do 
read-write actions go to the master database.



norbert.csongradi at services.hu wrote:
> Hi folks,
>
> I created a new storage class which supports MySQL replicated data source: one 
> master database where all the writing-related queries executed and it is 
> replicated to one or more slave databases where all the selects are executed.
>
> Please check it, try it and I'm eager to see any type of comments...
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> List: http://lists.rawmode.org/cgi-bin/mailman/listinfo/dbix-class
> Wiki: http://dbix-class.shadowcatsystems.co.uk/
> IRC: irc.perl.org#dbix-class
> SVN: http://dev.catalyst.perl.org/repos/bast/trunk/DBIx-Class/
> Searchable Archive: http://www.mail-archive.com/dbix-class@lists.rawmode.org/