Vintner
Plant a Vine

NoSQL

DynamoDB, Firestore, and Cosmos DB table configuration with key schema and billing modes.

NoSQL

The NoSQL section configures managed NoSQL database tables. Multiple tables can be added per vine.

Fields Per Table

FieldTypeDescription
NameText inputTable/collection name
Hash KeyText inputPartition key name (default: id)
Hash Key TypeSelectS (String), N (Number), B (Binary)
Range KeyText inputOptional sort key name
Range Key TypeSelectS, N, or B
Billing ModeSelectPAY_PER_REQUEST or PROVISIONED
Point-in-Time RecoveryToggleEnable continuous backups
Table TypeSelectstandard or global (multi-region replication)

Services by Provider

DynamoDB — fully managed key-value and document database

  • Hash key (partition key) + optional range key (sort key)
  • On-demand or provisioned capacity billing
  • Global tables for multi-region replication
  • KMS encryption at rest
  • Point-in-time recovery (continuous backups up to 35 days)

Firestore — document-oriented NoSQL database

  • Document-based model (collections → documents → fields)
  • Serverless with automatic scaling
  • Multi-region replication built-in

Firestore uses a document model rather than a key-value model. When converting from DynamoDB, hash/range keys map to document IDs. See Multi-Cloud Conversion.

Cosmos DB — globally distributed multi-model database

  • Partition key (maps to hash key)
  • Multiple APIs: SQL (document), Table (key-value), MongoDB, Cassandra, Gremlin
  • Multi-region writes for global distribution
  • Serverless or provisioned throughput (RU/s)

Billing Modes

ModeDescriptionBest For
PAY_PER_REQUESTPay per read/write operation, no capacity planningUnpredictable workloads, development
PROVISIONEDReserved read/write capacity unitsPredictable workloads, cost optimization

NoSQL tables show $0 in the cost sidebar because pricing is usage-based (per operation), not estimable from configuration alone. Actual costs depend on read/write patterns.

On this page