The problem with master slave architecture is consistency issues due to replication lag. What will happen when the master goes down without syncing some data to the slaves? For that we might need to incorporate other strategy too like synchronous replication, but then again it'll add to the latency. Good read anyway. Please keep writing. Thank you. 😊
No and No. Such operations are done asynchronously, whenever master receives write request it will pass them immediately to the replicas. Different solutions have different strategies to sync out of date data. For example, ElasticSearch uses Primary Term and Sequence Number in internal state to handle such issues.
Amazing Read! I had an inquiry that if I use a CDN over the site, does that improve the internals of my server/performance anyway, or is it just a location-wise distributed network?
Both. From location perspective, it will cache, store and optimize assets (video, images, html etc) to your nearest server so that it's served to you as fast as possible. From server perspective, it reduces the actual load on the server because the assets are already cached and stored in other places, thus no need to hit the servers.
Rafat Islam
Software Engineering
The problem with master slave architecture is consistency issues due to replication lag. What will happen when the master goes down without syncing some data to the slaves? For that we might need to incorporate other strategy too like synchronous replication, but then again it'll add to the latency. Good read anyway. Please keep writing. Thank you. 😊