Amazon Keyspaces (for Apache Cassandra)

Serverless Cassandra-compatible wide-column tables with on-demand capacity and encryption at rest.

Provider: aws
Kind: NoSQL database
Category: Data
Official docs: https://docs.aws.amazon.com/keyspaces/latest/devguide/how-it-works.html

Properties · 7 set by this component

property	type	values	required	kind default	this component
backupEnabled	boolean	—	no	false	▸ false
backupRetentionDays	integer	—	no	—	inherited
bucketing · advanced	boolean	—	no	false	inherited
capacityMode · component property	enum	on-demand \| provisioned	no	on-demand	inherited
conflictResolution	enum	none \| last-writer-wins \| vector-clock \| app-merge	no	—	inherited
consistency	enum	eventual \| tunable \| strong	no	eventual	▸ tunable
encryptionAtRest	boolean	—	no	false	▸ true
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ true
model	enum	key-value \| wide-column \| document	yes	—	▸ wide-column
multiRegion · component property	boolean	—	no	false	inherited
partitionKey	string	—	no	—	inherited
pointInTimeRecovery · component property	boolean	—	no	false	inherited
quorumReads · advanced	integer	—	no	—	inherited
quorumWrites · advanced	integer	—	no	—	inherited
replication	enum	single-region \| multi-region-single-leader \| multi-region-multi-leader \| leaderless	no	single-region	▸ single-region
replicationFactor	integer	—	no	—	▸ 3
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: "keyspaces", component: "aws-keyspaces" }

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 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 Azure Table Storageazure-table-storageazurenosql-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# Amazon Keyspaces (for Apache Cassandra): serverless wide-column tables reached over CQL.
3# "Amazon Keyspaces: How it works" states three copies of the data in multiple Availability Zones,
4# encryption at rest automatically enabled on table creation and TLS required for all client
5# connections; "Configure read/write capacity modes" names on-demand as the default capacity mode.
6schemaVersion: "1"
7type: "component"
8id: "aws-keyspaces"
9kind: "nosql-database"
10provider: "aws"
11docs: "https://docs.aws.amazon.com/keyspaces/latest/devguide/how-it-works.html"
12defaults:
13  managed: true
14  model: "wide-column"
15  consistency: "tunable"
16  replication: "single-region"
17  replicationFactor: 3
18  backupEnabled: false
19  encryptionAtRest: true
20properties:
21  capacityMode:
22    type: "enum"
23    values: ["on-demand", "provisioned"]
24    default: "on-demand"
25  pointInTimeRecovery:
26    type: "boolean"
27    default: false
28  multiRegion:
29    type: "boolean"
30    default: false

The same page as markdown, for an agent: /catalogue/components/aws-keyspaces.md