Azure Table Storage

Overview

We use Table Storage for key-value and simple entity data where Cosmos DB would be more database than you need. Partition key and row key are designed for the point reads and the narrow queries the application makes.

We set the storage account, access tier, and identity-based access, and we document which queries are intentionally not supported. If the access pattern grows into rich filters, we flag the move to Cosmos DB or SQL before the table becomes painful.

What we deliver

• Table design with partition key and row key for the real lookups
• Storage account settings and identity-based access
• A short list of supported and unsupported queries
• Retention or cleanup approach for entities that expire

Business benefits

• Simple lookups have a cheap store instead of a provisioned database
• Keys match the way the application reads, so scans are rare
• You have a written point at which the table should be replaced