A finance office runs OLTP on Aurora MySQL and also runs heavy reporting queries. How should traffic be separated for high-performing database access?
Select an answer to reveal the explanation.
Short Explanation
Don’t let the report printers sit on the same checkout lane as cashiers. Point reporting at Aurora reader endpoints and leave OLTP on the writer. Forcing reports onto the writer, killing replicas, or copying live volumes to instance store invites contention and risk.
Full Explanation
Amazon Aurora provides reader endpoints that distribute read traffic across Aurora Replicas while the writer endpoint serves OLTP mutations. Separating reporting onto readers improves scalability and protects transactional latency. Concentrating analytical load on the writer, removing replicas, or using ephemeral copies as the reporting source undermines high-performing database design.