You released an article today which said this "our prototype mapped entities in each inheritance hierarchy to their own separate Cosmos DB collections, but because of the way Cosmos DB pricing works, this could become unnecessarily expensive" and as a result you used a discriminator and pushed all entities into one collection.
The thing is thought that Azure changed its pricing to allow you to configure your RTU's globally for all collections and not by single collections.
So maybe you might want to offer an option instead. It seems you made a design decision based on Azures poor decision to do pricing per collection but now that they fixed that you should fix yours to. This is yet another example of Azures bad pricing model that lead to poor design decisions.
You released an article today which said this "our prototype mapped entities in each inheritance hierarchy to their own separate Cosmos DB collections, but because of the way Cosmos DB pricing works, this could become unnecessarily expensive" and as a result you used a discriminator and pushed all entities into one collection.
The thing is thought that Azure changed its pricing to allow you to configure your RTU's globally for all collections and not by single collections.
So maybe you might want to offer an option instead. It seems you made a design decision based on Azures poor decision to do pricing per collection but now that they fixed that you should fix yours to. This is yet another example of Azures bad pricing model that lead to poor design decisions.