HI Hugo MENDES ADMAZ,
The documented limit of 1000 collections per cluster in Azure Cosmos DB for MongoDB vCore is a general guideline rather than a strict enforcement. Here's what you need to know:
1. Actual Limit
- While the documentation states a limit of 1000 collections, your ability to create 1500 collections without errors suggests that the limit may be dynamically adjusted based on your cluster tier and workload.
- Azure Cosmos DB is designed to be flexible, and some limits may evolve over time as the service improves.
2. Outdated or Dynamic Limit
- The 1000 collection limit might be outdated or not strictly enforced for certain configurations. It's possible that higher-tier clusters (like M30) allow more collections due to increased resources.
3. Performance and Stability Considerations
- Exceeding the recommended limit could lead to:
- Increased latency for queries and operations.
- Higher memory and CPU usage, especially if collections have large indexes or frequent transactions.
- Challenges with scaling or managing the cluster.
- Monitor your cluster's metrics (e.g., CPU, memory, and throughput) to ensure stability as you add more collections.
Recommendations:
- Monitor Performance: Use Azure Monitor to track resource utilization and identify bottlenecks.
- Plan for Scaling: If you anticipate needing more collections, consider upgrading to a higher-tier cluster or exploring sharding strategies.
I would request you to refer the below mentioned links for more information
1.Service Limits in Azure Cosmos DB for MongoDB vCore
2.Azure Cosmos DB service quotas
3.MicrososftDoc
I hope this information helps. Please do let us know if you have any further queries.