Hi All,
I read from the MySource Matrix Architecture Options document that we can setup a Dynamic writable publishing platform, in which there are Master and Slave MySource Matrix servers.
It mentions the followings
[indent]MySource Matrix has a configuration option that allows “read” database queries (SELECT statements) to be
passed to one server while “write” queries (INSERT, UPDATE and DELETE statements) are made to another.
Changes made to the master (write) database and automatically replicated back through to the publishing
server using master/slave database replication. Its is important to note that file system changes are not
passed back to the master MySource Matrix application server.[/indent]
I search through the documentations, but couldn't find much about this.
Can anyone tell me about this?
Tanks a lots.
Cheers,
Joe
You really need to contact Squiz about this to get the right information.
But the main part of it are the different DSNs that Matrix supports. You have 3 main DSNs that are used for reading, writing inside transactions and writing outside of transactions. You then have DSNs for the cache and search systems. These different connection strings allow you to have Matrix talk to different databases based on what it is doing, and then handle replication with other tools.