A company is developing a fleet management application. The application will store real-time telemetry from 50,000 delivery vehicles. The workload has a read/write ratio of 80% writes and 20% reads. The data must be distributed across three Azure regions to support global users, and the solution must avoid partition throttling while maintaining high availability. Which configuration should you recommend for the Azure Cosmos DB container?
- Use vehicleId as the partition key and enable multi-region replication.Cevap
- BUse vehicleStatus as the partition key and enable locally redundant storage (LRS).
- CUse vehicleId as the partition key and authenticate clients using a Shared Access Signature (SAS) token with a 5-year duration.
- DUse vehicleId as the partition key and configure locally redundant storage (LRS) to minimize costs.
Cevap
Use vehicleId as the partition key and enable multi-region replication.
The correct option is to use vehicleId as the partition key and enable multi-region replication. vehicleId is a high-cardinality key that distributes writes evenly across logical partitions, while multi-region replication ensures low latency and high availability across the three target regions.
Adım Adım Çözüm
Anahtar Kavram
Selecting high-cardinality partition keys and configuring appropriate global distribution in Azure Cosmos DB to prevent throttling and ensure high availability.