Scalar Pricing
Data Management and Byzantine Fault Detection Middleware
Deployed on-premise, single-cloud, multi-cloud, or hybrid-cloud.
Functionality | Community Edition | ScalarDB Enterprise Edition (Standard) | ScalarDB Enterprise Edition (Premium) |
|---|---|---|---|
Transaction processing across databases | ◯ | ◯ | ◯ |
Clustering | - | ◯ | ◯ |
Non-transactional storage operations | - | ◯ | ◯ (3.14+) |
Authentication/authorization | - | ◯ | ◯ |
SQL interface (SQL API, JDBC, Spring Data JDBC, and LINQ) | - | ◯ | ◯ |
GraphQL Interface | - | - | ◯ |
Encryption | - | - | ◯ (3.14+) |
Vector search interface | - | - | ◯ (3.14+) |
DESCRIPTION OF PODS
*1 Each pod is considered as 1 unit with 2vCPU / 4GB memory. If the size of a single pod exceeds this resource, the calculation will be done by using either the number of vCPUs rounded up by dividing it with 2vCPU or the memory size rounded up by dividing it with 4GB, whichever is greater.
** vCPU refers to a virtual CPU. For instance, if you're using Kubernetes, it corresponds to the CPU you configure in Kubernetes. In AWS, Microsoft Azure, and Google Cloud, this is denoted as vCPUs, while in Oracle Cloud Infrastructure (OCI), it is referred to as OCPUs. For the concept of vCPUs for each cloud provider, please refer to the following links: