Skip to main content
Version: 3.13
Features and pricing

Configurations for the Underlying Databases of ScalarDB

This document explains how to configure the underlying databases of ScalarDB to make applications that use ScalarDB work correctly and efficiently.

General requirements for the underlying databases​

ScalarDB requires each underlying database to provide certain capabilities to run transactions and analytics on the databases. This document explains the general requirements and how to configure each database to achieve the requirements.

Transactions​

ScalarDB requires each underlying database to provide at least the following capabilities to run transactions on the databases:

  • Linearizable read and conditional mutations (write and delete) on a single database record.
  • Durability of written database records.
  • Ability to store arbitrary data beside application data in each database record.

Analytics​

ScalarDB requires each underlying database to provide the following capability to run analytics on the databases:

  • Ability to return only committed records.
note

You need to have database accounts that have enough privileges to access the databases through ScalarDB since ScalarDB runs on the underlying databases not only for CRUD operations but also for performing operations like creating or altering schemas, tables, or indexes. ScalarDB basically requires a fully privileged account to access the underlying databases.

How to configure databases to achieve the general requirements​

Select your database for details on how to configure it to achieve the general requirements.

Transactions

  • Use a single primary server or synchronized multi-primary servers for all operations (no read operations on read replicas that are asynchronously replicated from a primary database).
  • Use read-committed or stricter isolation levels.

Analytics

  • Use read-committed or stricter isolation levels.

Recommendations​

Properly configuring each underlying database of ScalarDB for high performance and high availability is recommended. The following recommendations include some knobs and configurations to update.

note

ScalarDB can be seen as an application of underlying databases, so you may want to try updating other knobs and configurations that are commonly used to improve efficiency.

  • Use read-committed isolation for better performance.
  • Follow the performance optimization best practices for each database. For example, increasing the buffer size (for example, shared_buffers in PostgreSQL) and increasing the number of connections (for example, max_connections in PostgreSQL) are usually recommended for better performance.