how effective creating 2 database with same content? 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.
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).