This website uses cookies to ensure you get the best experience.
Learn more.
A new service needs per-item conditional updates at very high scale and predictable key-based reads. Relational joins are not required. Which database design is most appropriate?
Published
- Use Route 53 records as the primary transaction table.
- Store all records in one S3 object and overwrite it for every update.
- Use DynamoDB with keys designed for the access patterns and conditional writes for state transitions.
- Use a single unsharded in-memory process with no durable store.
Comments — 0
Sign in to comment