Azure Table Storage

Schemaless key/attribute NoSQL store addressed by partition key and row key.

Provider: azure
Kind: NoSQL database
Category: Data
Official docs: https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-overview

Properties · 6 set by this component

property	type	values	required	kind default	this component
backupEnabled	boolean	—	no	false	inherited
backupRetentionDays	integer	—	no	—	inherited
bucketing · advanced	boolean	—	no	false	inherited
conflictResolution	enum	none \| last-writer-wins \| vector-clock \| app-merge	no	—	inherited
consistency	enum	eventual \| tunable \| strong	no	eventual	▸ strong
encryptionAtRest	boolean	—	no	false	▸ true
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ true
maxEntitySizeMib · component property	integer	—	no	1	inherited
maxPropertiesPerEntity · component property	integer	—	no	252	inherited
model	enum	key-value \| wide-column \| document	yes	—	▸ key-value
partitionKey	string	—	no	—	▸ PartitionKey
quorumReads · advanced	integer	—	no	—	inherited
quorumWrites · advanced	integer	—	no	—	inherited
redundancy · component property	enum	lrs \| zrs \| grs \| gzrs \| ra-grs \| ra-gzrs	no	lrs	inherited
replication	enum	single-region \| multi-region-single-leader \| multi-region-multi-leader \| leaderless	no	single-region	▸ single-region
replicationFactor	integer	—	no	—	inherited
tombstoneTtlDays · advanced	integer	—	no	—	inherited

Rules that apply · 2

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Multi-leader store without a conflict policywarning

multi-leader-store-without-conflict-policy

Multi-leader replication accepts concurrent writes in several regions. With no conflict resolution policy declared, divergent replicas are reconciled by accident rather than by design.

— all of these hold:
— the node's `replication` is "multi-region-multi-leader"
— any of these hold:
— the node's `conflictResolution` has no value
— the node's `conflictResolution` is "none"

Read-heavy datastore without a cachewarning

read-heavy-path-without-cache

The design states a read-heavy workload and application servers read this datastore directly, yet the design has no cache anywhere. Every read pays a database round trip.

— all of these hold:
— the design requirement `traffic.readWriteRatio` is a number greater than 10
— the node has at least one synchronous incoming edge from an app-server
— this does not hold:
— the design contains a node of kind cache

Use it in a design

nodes:
  - { id: "table-storage", component: "azure-table-storage" }

Other NoSQL database products · 46

ApsaraDB for HBasealibaba-apsaradb-hbasealibabacloudnosql-database ApsaraDB for MongoDBalibaba-apsaradb-mongodbalibabacloudnosql-database Lindormalibaba-lindormalibabacloudnosql-database Tablestorealibaba-tablestorealibabacloudnosql-database Amazon CloudFront KeyValueStoreaws-cloudfront-keyvaluestoreawsnosql-database Amazon Cognito Syncaws-cognito-syncawsnosql-database Amazon DocumentDBaws-documentdbawsnosql-database AWS HealthLakeaws-healthlakeawsnosql-database Amazon Keyspaces (for Apache Cassandra)aws-keyspacesawsnosql-database Amazon DynamoDBdynamodbawsnosql-database Azure Cosmos DBazure-cosmos-dbazurenosql-database Azure DocumentDBazure-documentdbazurenosql-database Azure Health Data Servicesazure-health-data-servicesazurenosql-database Azure Managed Instance for Apache Cassandraazure-managed-cassandraazurenosql-database Workers KVcloudflare-workers-kvcloudflarenosql-database Apache Accumuloaccumulonosql-database Aerospike Databaseaerospikenosql-database Apache Cassandracassandranosql-database Couchbasecouchbasenosql-database Apache CouchDBcouchdbnosql-database DataStax Enterprisedatastax-enterprisenosql-database FoundationDBfoundationdbnosql-database Apache HBasehbasenosql-database MarkLogic Servermarklogicnosql-database MongoDBmongodbnosql-database MongoDB Atlasmongodb-atlasnosql-database Generic NoSQL databasenosql-databasenosql-database NoSQL storenosql-storenosql-database OrientDBorientdbnosql-database RavenDBravendbnosql-database RethinkDBrethinkdbnosql-database Riak KVriaknosql-database ScyllaDBscylladbnosql-database TiKVtikvnosql-database YDBydbnosql-database Google Cloud Bigtablebigtablegcpnosql-database Google Cloud Firestorefirestoregcpnosql-database Cloud Healthcare APIgoogle-cloud-healthcare-apigcpnosql-database Firebase Realtime Databasegoogle-firebase-realtime-databasegcpnosql-database Firestore in Datastore modegoogle-firestore-datastore-modegcpnosql-database

and 6 more → NoSQL database page

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Azure Table Storage: schemaless key/attribute store in a storage account, addressed by a
3# partition key and a row key ("Introduction to Table storage"). Storage accounts are LRS and
4# encrypted at rest by default ("Data redundancy - Azure Storage").
5schemaVersion: "1"
6type: "component"
7id: "azure-table-storage"
8kind: "nosql-database"
9provider: "azure"
10docs: "https://learn.microsoft.com/en-us/azure/storage/tables/table-storage-overview"
11defaults:
12  model: "key-value"
13  consistency: "strong"
14  replication: "single-region"
15  partitionKey: "PartitionKey"
16  encryptionAtRest: true
17  managed: true
18properties:
19  redundancy:
20    type: "enum"
21    values: ["lrs", "zrs", "grs", "gzrs", "ra-grs", "ra-gzrs"]
22    default: "lrs"
23  maxEntitySizeMib:
24    type: "integer"
25    default: 1
26  maxPropertiesPerEntity:
27    type: "integer"
28    default: 252

The same page as markdown, for an agent: /catalogue/components/azure-table-storage.md