Adding a compression cost optimization section to the Cosmos DB docs #4151
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR adds further optimisations to the Cosmos DB state management, focusing on cost savings. The section breaks down how Cosmos DB RU/s are calculated and how developers can use compression algorithms to reduce the overall size of the object they are reading and writing to state and subsequently reduce the number of RU/s used. This is inspired by the work of my colleague who reduced our RU usage by 97% which he wrote about here: Maximizing Efficiency in Scalable Systems: Part I — Reducing costs of consumption-based state stores by up to 97% when using Dapr actors at scale
Issue reference
Closes #4047