Compare reads to writes before choosing what to scale.

Once you have converted the traffic estimate to per-second rates, look at the ratio between reads and writes. If a service gets one new item for every hundred lookups, effort belongs where the traffic is: caching popular items and spreading reads over replicas. A few dozen writes a second is a small load that one primary handles comfortably.

Read it once, then a question tests whether the trick stuck.