This topic answers frequently asked questions about geo-redundant dual-read.
Geo-redundant dual-read only protects read traffic. How is write traffic protected?
Geo-redundant dual-read protects only read traffic. You can protect write traffic using other disaster recovery architectures. If no other disaster recovery architecture is used to protect write traffic, the default solution is single-point writing.
What dimensions are used to distinguish between read and write traffic?
Traffic is distinguished on the application side. You can separate traffic using different domain names, different URIs under the same domain name, or different IP addresses.
What are the scenarios for geo-redundant dual-read?
This solution is designed for read-heavy services, such as shopping guides, information portals, and query services.
What is the business transformation cost for geo-redundant dual-read?
The main requirement is that your application can distinguish read operations. No code changes are required for the application itself. In this solution, inbound traffic connects to the MSFE layer, and the underlying databases are synchronized.