Skip to main content
Version: 3.16

Requirements

This page describes the required tools and their versions to use ScalarDB correctly.

Client SDK

Because ScalarDB is written in Java, the easiest way to interact with ScalarDB is to use the Java client SDKs:

Java

The following Java Development Kits (JDKs) are verified and supported.

.NET

ScalarDB is provided as a gRPC server called ScalarDB Cluster, which also has a .NET client SDK that wraps the .NET client generated from the proto file.

The following .NET versions are verified and supported:

Other languages

ScalarDB Cluster uses gRPC version 1.65.0, so you can create your own client by using the generated clients of your preferred languages.

Databases

ScalarDB is middleware that runs on top of the following databases and their versions.

Relational databases

VersionOracle Database 23aiOracle Database 21cOracle Database 19c
ScalarDB 3.16
ScalarDB 3.15
ScalarDB 3.14
ScalarDB 3.13
ScalarDB 3.12
ScalarDB 3.11
ScalarDB 3.10
ScalarDB 3.9
ScalarDB 3.8
ScalarDB 3.7

NoSQL databases

VersionDynamoDB
ScalarDB 3.16
ScalarDB 3.15
ScalarDB 3.14
ScalarDB 3.13
ScalarDB 3.12
ScalarDB 3.11
ScalarDB 3.10
ScalarDB 3.9
ScalarDB 3.8
ScalarDB 3.7
note

For details on how to configure each database, see Configurations for the Underlying Databases of ScalarDB.

Permission requirements

This section describes the required permissions for using ScalarDB with its supported databases.

Oracle Database

ScalarDB requires the following actions to be granted to the Oracle Database user that ScalarDB uses to access Oracle Database:

  • CREATE SESSION
  • CREATE USER
  • DROP USER
  • ALTER USER
  • CREATE ANY TABLE
  • DROP ANY TABLE
  • CREATE ANY INDEX
  • DROP ANY INDEX
  • ALTER ANY TABLE
  • SELECT ANY TABLE
  • INSERT ANY TABLE
  • UPDATE ANY TABLE
  • DELETE ANY TABLE

IBM Db2

ScalarDB requires the following database authorities to be granted to the Db2 user that ScalarDB uses to access Db2:

  • DBADM
  • DATAACCESS

MySQL

ScalarDB requires the following privileges to be granted to the MySQL user that ScalarDB uses to access MySQL:

  • CREATE
  • DROP
  • INDEX
  • ALTER
  • SELECT
  • INSERT
  • UPDATE
  • DELETE

PostgreSQL

ScalarDB requires the following PostgreSQL database role to be granted to the PostgreSQL role that ScalarDB uses to access PostgreSQL:

  • SUPERUSER

MariaDB

ScalarDB requires the following privileges to be granted to the MariaDB user that ScalarDB uses to access MariaDB:

  • CREATE
  • DROP
  • INDEX
  • ALTER
  • SELECT
  • INSERT
  • UPDATE
  • DELETE

SQL Server

ScalarDB requires the following database roles to be granted to the SQL Server user that ScalarDB uses to access SQL Server:

  • db_ddladmin
  • db_datareader
  • db_datawriter

YugabyteDB

ScalarDB requires the following YugabyteDB database role to be granted to the YugabyteDB role that ScalarDB uses to access YugabyteDB:

  • SUPERUSER

Amazon DynamoDB

ScalarDB requires the following actions to be granted to the AWS IAM user that ScalarDB uses to access DynamoDB:

  • dynamodb:ConditionCheckItem
  • dynamodb:PutItem
  • dynamodb:ListTables
  • dynamodb:DeleteItem
  • dynamodb:Scan
  • dynamodb:Query
  • dynamodb:UpdateItem
  • dynamodb:DeleteTable
  • dynamodb:UpdateContinuousBackups
  • dynamodb:CreateTable
  • dynamodb:DescribeTable
  • dynamodb:GetItem
  • dynamodb:DescribeContinuousBackups
  • dynamodb:UpdateTable
  • application-autoscaling:RegisterScalableTarget
  • application-autoscaling:DeleteScalingPolicy
  • application-autoscaling:PutScalingPolicy
  • application-autoscaling:DeregisterScalableTarget
  • application-autoscaling:TagResource

Apache Cassandra

ScalarDB requires the following actions to be granted to the Cassandra role that ScalarDB uses to access Cassandra:

  • CREATE
  • DROP
  • ALTER
  • SELECT
  • MODIFY

Kubernetes

ScalarDB is provided as a Pod on the Kubernetes platform in production environments. ScalarDB supports the following platforms and tools.

Platform

Package manager