A city wants high-scale citizen profile lookups in NoSQL but must keep tax billing in a relational system with strong ACID controls. What migration pattern fits?
Select an answer to reveal the explanation.
Short Explanation
You do not have to tip the whole city stack into NoSQL just because profiles got huge. Keep the tax ledger on the relational side for ACID, and park only the high-scale profile slice in NoSQL. All-or-nothing moves and CSV-only designs are the wrong swing of the hammer.
Full Explanation
Partial migration is a common RDBMS-to-NoSQL pattern: move the workload that needs scale and flexible access while retaining relational stores for transactional domains. Citizen profiles at high read scale are a typical NoSQL candidate; tax billing usually remains relational for integrity. Overnight all-system graph moves, deleting billing after any NoSQL collection appears, or replacing online stores with nightly CSV alone are unsafe or incomplete patterns.