how effective creating 2 database with same content?

All we need is an easy explanation of the problem, so here it is.

I’m in a dilemma if creating redundant database will speed up the access considering only the CRUD factor.

Is it effective to create a dedicated DB for creating/updating/deleting records
and a separate DB for viewing only?

Currently using MySQL.

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

This is called Write masters with Read slaves. Check out MySQL replication. You’ll find an interesting document here (check out the slides) – but you probably won’t be needing the level of availability of Booking.com, but hey, who knows? :-).

There are many different replication/HA topologies, but this will give you a start. Also, see here (Andrew Morgan is the author of MySQL Cluster).

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply