ApsaraDB for HBase

alibabacloudNoSQL databasealibaba-apsaradb-hbase

Managed wide-column NoSQL database compatible with Apache HBase, serving petabyte-scale data at millisecond latency.

Provider
alibabacloud
Category
Data
Properties · 4 set by this component
propertytypevaluesrequiredkind defaultthis component
backupEnabledboolean—nofalseinherited
backupRetentionDaysinteger—no—inherited
bucketing · advancedboolean—nofalseinherited
coldStorage · component propertyboolean—no—inherited
conflictResolutionenumnone | last-writer-wins | vector-clock | app-mergeno—inherited
consistencyenumeventual | tunable | strongnoeventual▸ strong
edition · component propertyenumstandard | performance-enhanced | serverlessno—inherited
encryptionAtRestboolean—nofalseinherited
hbaseVersion · component propertyenum1-1 | 2-0no—inherited
instancesinteger—no—inherited
managedboolean—nofalse▸ true
modelenumkey-value | wide-column | documentyes—▸ wide-column
partitionKeystring—no—inherited
quorumReads · advancedinteger—no—inherited
quorumWrites · advancedinteger—no—inherited
replicationenumsingle-region | multi-region-single-leader | multi-region-multi-leader | leaderlessnosingle-region▸ single-region
replicationFactorinteger—no—inherited
tombstoneTtlDays · advancedinteger—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-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-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: "apsaradb-hbase", component: "alibaba-apsaradb-hbase" }
Other NoSQL database products · 46
ApsaraDB for MongoDBalibaba-apsaradb-mongodbalibabacloudnosql-databaseLindormalibaba-lindormalibabacloudnosql-databaseTablestorealibaba-tablestorealibabacloudnosql-databaseAmazon CloudFront KeyValueStoreaws-cloudfront-keyvaluestoreawsnosql-databaseAmazon Cognito Syncaws-cognito-syncawsnosql-databaseAmazon DocumentDBaws-documentdbawsnosql-databaseAWS HealthLakeaws-healthlakeawsnosql-databaseAmazon Keyspaces (for Apache Cassandra)aws-keyspacesawsnosql-databaseAmazon DynamoDBdynamodbawsnosql-databaseAzure Cosmos DBazure-cosmos-dbazurenosql-databaseAzure DocumentDBazure-documentdbazurenosql-databaseAzure Health Data Servicesazure-health-data-servicesazurenosql-databaseAzure Managed Instance for Apache Cassandraazure-managed-cassandraazurenosql-databaseAzure Table Storageazure-table-storageazurenosql-databaseWorkers KVcloudflare-workers-kvcloudflarenosql-databaseApache Accumuloaccumulonosql-databaseAerospike Databaseaerospikenosql-databaseApache Cassandracassandranosql-databaseCouchbasecouchbasenosql-databaseApache CouchDBcouchdbnosql-databaseDataStax Enterprisedatastax-enterprisenosql-databaseFoundationDBfoundationdbnosql-databaseApache HBasehbasenosql-databaseMarkLogic Servermarklogicnosql-databaseMongoDBmongodbnosql-databaseMongoDB Atlasmongodb-atlasnosql-databaseGeneric NoSQL databasenosql-databasenosql-databaseNoSQL storenosql-storenosql-databaseOrientDBorientdbnosql-databaseRavenDBravendbnosql-databaseRethinkDBrethinkdbnosql-databaseRiak KVriaknosql-databaseScyllaDBscylladbnosql-databaseTiKVtikvnosql-databaseYDBydbnosql-databaseGoogle Cloud Bigtablebigtablegcpnosql-databaseGoogle Cloud Firestorefirestoregcpnosql-databaseCloud Healthcare APIgoogle-cloud-healthcare-apigcpnosql-databaseFirebase Realtime Databasegoogle-firebase-realtime-databasegcpnosql-databaseFirestore in Datastore modegoogle-firestore-datastore-modegcpnosql-database
and 6 more → NoSQL database page
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# ApsaraDB for HBase: "a fully managed, cloud-native NoSQL database service compatible with open source
# Apache HBase" for petabyte-scale wide-column data at millisecond latency ("What is ApsaraDB for HBase?").
# "Standard Edition, Performance-enhanced Edition, Serverless Edition" states Standard Edition is 100%
# compatible with open source HBase V1.1.2 and V2.0.0 while Performance-enhanced Edition is built on Lindorm;
# both inherit the strongly consistent single-region reads and writes of Apache HBase. No backup or
# encryption default is documented, so neither is set.
schemaVersion: "1"
type: "component"
id: "alibaba-apsaradb-hbase"
kind: "nosql-database"
provider: "alibabacloud"
docs: "https://www.alibabacloud.com/help/en/hbase/"
defaults:
  managed: true
  model: "wide-column"
  consistency: "strong"
  replication: "single-region"
properties:
  edition:
    type: "enum"
    values: ["standard", "performance-enhanced", "serverless"]
  hbaseVersion:
    type: "enum"
    values: ["1-1", "2-0"]
  coldStorage:
    type: "boolean"

The same page as markdown, for an agent: /catalogue/components/alibaba-apsaradb-hbase.md