This website uses cookies to ensure you get the best experience.
Learn more.
A candidate partition key has only three possible values for a rapidly growing write-heavy dataset. What concern should the design review prioritize?
Published
- Automatic loss of all transactional support
- Too many distinct routing values
- Guaranteed zero request-unit cost
- Low cardinality and concentration of data and requests
Comments — 0
Sign in to comment