What should a solutions architect do to meet these requirements?
Create a read replica. Move reporting queries to the read replica.
Create a read replica. Distribute the ordering application to the primary DB instance and the read replica.
Migrate the ordering application to Amazon DynamoDB with on-demand capacity.
Schedule the reporting queries for non-peak hours.
Explanations:
Creating a read replica allows the reporting queries to be offloaded from the primary database, reducing load and preventing timeouts during order processing. Employees can run their reporting queries against the read replica without impacting the performance of the ordering application.
While a read replica can help with reporting, distributing the ordering application across the primary DB instance and the read replica is not feasible or advisable. The ordering application should always interact with the primary instance to ensure data consistency and integrity.
Migrating to Amazon DynamoDB may reduce the risk of timeouts but changes the database technology and structure, which could introduce significant overhead and complexity. Additionally, this does not directly address the need to run reporting queries concurrently with order processing.
Scheduling reporting queries for non-peak hours might reduce conflicts but does not solve the immediate problem of timeouts during business hours when the queries are needed. It also limits the flexibility for employees who require timely access to reporting data.
From my point of view, the answer is:
Create a read replica. Move reporting queries to the read replica.