Q: 5
A company stores a large dataset for an online advertising business in an Amazon RDS for MySQL DB
instance. The company wants to run business reporting queries on the data without affecting write
operations to the DB instance.
Which solution will meet these requirements?
Options
Discussion
Option A had something like this in a mock and read replicas are the usual AWS way to separate reporting reads from production writes.
A . Read replicas are meant for offloading read-heavy stuff like reporting so the primary keeps handling writes smoothly. Scaling up (C) just makes everything share one bigger box, doesn't separate reads from writes. Anyone see it different?
A
Yeah, A is right here. Using read replicas lets you run reporting queries without impacting the main RDS write workload.
C or A? I think it's supposed to be A with read replicas for reporting but not totally sure since horizontal scaling can be confusing with RDS. Anyone else see something like this?
C. scaling up the DB instance feels like it would let both writes and reporting work better at once, right?
Y AWS makes this so convoluted sometimes, but it's A for sure.
Read replicas are built for this use case. A
A makes more sense is what I picked on something almost identical in a mock. Read replicas are made for offloading heavy reporting reads so writes on the main DB instance don't get slowed down. Scaling up (C) just throws more power at it, doesn't isolate traffic. Not 100% but pretty confident here, anyone see it different?
Nah, it's not B-ELB can't balance database read traffic like that. A is the right move here.
Be respectful. No spam.
