Re: Database connections to Slave

[Jesse Toninger]

There are definitely more qualified people than me on these boards to answer this but in the interest of community, here goes.

In a typical setup your slave server would be set to read only, as in the case of most applications the vast majority of database operations are reads. Your application would then be structured to send any write operations directly back to the master, which would then push down.

It requires your knowledge of what your application is doing at a given time to manage this.

You CAN set up writable slaves, or Master-Master replication, but these come with a whole host of other potential risks others could speak to better than I. You basically better be sure you would never have conflicting data entered into both databases at once.

Speaking very much as a DB layperson, stick with Read-Only slaves unless you have a specific reason why that wont work