Partitioned Collections with < 10k RU/s
Please allow partitioned collections with fewer than 10k RU reserved.
I really would like to use partitioned collection but according and the pricing model $6/month for each 100 RU seems fair. But the minimum RU/s for partitioned collections are > 10.000 RU/s which is min $600 a month.
We are pleased to announce that partitioned collections have an entry point 75% cheaper than before. Instead of provisioning 10,100 RU/sec as a minimum, you can now provision a partitioned collection at 2,500 RU/sec and scale in increments of 100 RU/sec. Partitioned collections enable you to dynamically scale your provisioning from as low as 2,500 RU/sec to millions of RU/sec with no limit on storage consumption.
Please download SDK 1.12.0+ or use the Azure Portal to provision these collections.
Dane Creighton commented
Any plans to reduce this further than 2500 RU's ? Ideally it would be 400 RU's the same as a single partition collection as 2500 RU's is NZD is still > $250 a month (Australia East Server). The price is fine for if you require those resources but not for when you have to purchase these resources not to be used, only so you can have a forward design that will scale well down the track.
Azure DocumentDB Team commented
Thanks Ethan for your feedback. We are currently in Private Preview of the lower throughput limit so feel free to contact us through firstname.lastname@example.org to get early access to the lower limit offer. Also, we are working on a smooth transition from single partition to partitioned collection.
Azure DocumentDB team
We really need the storage not the RU's at the start, either drop the minimum RUs immediately or make the migration from single to partitioned collection a matter of a mouseclick in the azure portal. That would be even better than the absolutely nonsense migration with the local copy you offer now. We just need a way to easily scale and do instant migrations to partitioned collections if needed
MUST HAVE!! Hurry up with this please as it is the most major blocker for us right now! give us a timeline! 100 RUs as a selectable minimum!
Ryan Lamansky commented
Given that the partition key must be decided at design-time, the lower the better as there can be quite a gap between early development and production. I'd like to see 100 RUs as the minimum to have a comparable price to the cheapest SQL Database option.
This is a major roadblock for us so hopefully you can handle this soon
Really good news John. Thanks for the info. Some timeframe would be nice though
Totally agree. This is a must!