A property-assessment catalog is read-heavy for public browsing while writes remain modest on the primary. Latency for browse traffic is too high. Which performance approach fits?
Select an answer to reveal the explanation.
Short Explanation
Browsers shouldn’t all pile onto the one writer. Spin read replicas and a cache so the assessment catalog stays snappy while writes keep a quieter primary.
Full Explanation
Read replicas and caching reduce read latency and offload the primary for browse-heavy catalogs. Serving all reads from a single writer, only growing disks, or removing indexes worsens performance. Combining replicas with a cache tier is a standard way to meet performance objectives for municipal property data.