The backend of my project is very read-heavy and in it's current
implementation (Rails), we have been very successful with using
replication. To achieve this we keep a mysql connection manager object
that checks if a given statement is a write or a read and switches
between the master and the replicated slave as needed. Has anyone done
something like this with erlydb? If so, how?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"erlyweb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/erlyweb?hl=en
-~----------~----~----~----~------~----~------~--~---
