A bank requires strict ACID transactions, even at the cost of more design work. What matters?
Why D is the answer
Choosing a store that supports them
When strict ACID transactions are required, you must choose a store that supports them.
In detail
- A store must support ACID transactions for this to hold.
- ACID stands for atomic, consistent, isolated and durable.
Use case
An illustrative scenario, not a real incident.
A bank's transfers must never half-complete, so it chooses a store that supports ACID, even with more design work.
See it in different ways
mindmap
root((Stores))
BigQuery
Analytics
Bigtable
Key lookups at scale
Spanner
Global relational
AlloyDB
PostgreSQL
Firestore
Mobile documents
Memorystore
Microsecond cache
Cloud Storage
Objectsflowchart TD
Q{"Are strict transactions required?"}
Q -->|"Yes"| A0["Store with ACID support"]
Q -->|"No"| A1["Wider choice"]Key point: Choose storage by its guarantees.
Why the other options are wrong
- A. Using the lowest-latency cache only
- A cache does not give transactions.
- B. Choosing a file format for dashboards
- A file format does not give transactions.
- C. Using a longer retention on logs
- Logs are unrelated.