A municipal finance office must post multi-row ledger entries that either all commit or all roll back across related accounts. Which store is the most appropriate primary system?
Select an answer to reveal the explanation.
Short Explanation
City ledgers are like a balanced checkbook—every debit needs its matching credit, no half-done entries. That is classic relational ACID territory. Keep the money system on an RDBMS and save flexible NoSQL for less picky workloads.
Full Explanation
Financial ledgers commonly require atomic multi-row updates so related account lines remain consistent. Relational databases provide mature ACID transaction support for those cross-row commits and rollbacks. Many NoSQL designs optimize for distribution and flexible documents rather than multi-row transactional integrity. Using a relational system of record for municipal finance avoids inconsistent partial posts that would be unacceptable in accounting.