Using one bucket vs. many
The docs mention a few reasons why a popular logical 'model' or object class might need to go into its own bucket, '10.6.5. View Writing Best Practice'. For example having one bucket for the 'players' and another for the 'monsters' - as compared to putting them all in a single bucket with a jsonType:'player' or jsonType:'monster' in the document.
Once it's decided we have to have a separate bucket once for a model type, it might be easier from an architectural standpoint to simply repeat this pattern for all object types.
My question is, is there any *disadvantage* to separating every type of object into a different bucket? I.e. if there are say 10 models, would having 10 buckets be less performant than coalescing a subset of those into a single bucket, and using a 'jsonType' field to maintain type info? What about 50 models?
Or are there any other disadvantages, for example it's harder to calculate memory requirements?