Increase 10GB limit on non partitioned collection
Give there is a hard 10GB limit on a non-partitioned collection, and partition collections are much more expensive, with no auto-upgrade and code changes required to migrate to partitions, a larger size limit on non partitioned collection is much needed.
Quick update: We reduced the entry point to partitioned collections by 75% to make it more cost effective for applications that need high storage but low throughput.
Please see https://azure.microsoft.com/en-us/blog/azure-documentdb-entry-point-for-partitioned-collections-now-75-cheaper/ for details, and email us at email@example.com for any questions.
Satya Tanwar commented
Completely agree with @Jon McGuire.
Jon McGuire commented
75% cheaper is still unreasonably expensive for anything short of a well-funded project destined for production deployment.
This means you're completely screwing up one of Microsoft's traditional strong points: making it easy for developers to get and use your products. I have the VS Enterprise MSDN credit and even minor Cosmos experimentation chews through that allotment. It's made worse when Azure is spending my credit hour-by-hour while I search through the vast array of disorganized and outdated documentation. I'm getting the feeling things are changing so quickly not even your own people can stay on top of it. As an architect, it's getting harder and harder to justify putting up with this.