City utility billing OLTP must remain highly available after migration, while finance wants multi-year usage analytics that currently hammer the same on-premises SQL Server. Which database-platform selection should architects make for the new architecture?
Select an answer to reveal the explanation.
Short Explanation
The cash register and the research library should not be the same machine. Keep billing on RDS or Aurora so payments stay snappy, and send the big history questions somewhere built for analytics. Super-sizing one SQL box is how month-end reports take down payment night.
Full Explanation
After migration, OLTP systems of record such as utility billing belong on Amazon RDS or Amazon Aurora sized for transactional SLAs. Heavy analytics should be offloaded to a purpose-built path such as Amazon Redshift or Amazon Athena on S3 rather than endlessly growing the OLTP instance. Using OpenSearch or S3 Select as the billing system of record, or forcing mixed workloads onto one box, mis-selects the database platform for each access pattern.