ScalarDB 3.8 has been released!

We recently released ScalarDB 3.8.0 as a new minor version of ScalarDB. The new release includes ScalarDB Cluster, which makes it easier to manage microservice transactions with ScalarDB. This release also adds a Spring Data JDBC integration and extends the ScalarDB GraphQL queries.

This blog post briefly describes Scalar DB Cluster, the Spring Data JDBC integration, and the GraphQL query extensions.

ScalarDB Cluster

ScalarDB has provided an interface to manage microservice transactions easily. However, when multiple interactions between microservices are performed within a single transaction, application developers must manage the destination of the transaction on the application side, placing a heavy burden on application developers. ScalarDB Cluster is designed to solve this problem. Specifically, ScalarDB Cluster consists of multiple servers with ScalarDB functionality. In addition, these servers have routing capabilities that route transaction requests to a server that should handle the transaction. As a result, application developers no longer need to manage the destination of transactions on the application side, and each microservice works correctly regardless of which server it communicates with. This new component makes it easier to manage microservice transactions with ScalarDB.

For more information on the ScalarDB Cluster, see this document.

Spring Data JDBC support

This release adds integration for Spring Data JDBC, the database abstraction layer in the Spring Framework. This allows you to develop ScalarDB applications using the Spring Data interface, making it even easier to use ScalarDB, especially for Spring Data users.

You can develop ScalarDB applications using the Spring Data JDBC API, as shown below:

Example of Spring Data JDBC integration

For more information on the ScalarDB Spring Data JDBC integration, see this document.

GraphQL query extensions

Starting with this release, ScalarDB GraphQL allows ScanAll queries that can scan data across partitions and Get/Scan queries with secondary indexes.

For the ScanAll query, you can retrieve all the data in the “bank” table by issuing the following query:

Example of ScanAll in GraphQL

You can also specify a “limit” parameter to limit the number of results returned by the query, as shown below:

Example of ScanAll with limit in GraphQL

And for the Get/Scan queries with secondary indexes, you can execute them by issuing queries as follows:

Example of Get/Scan with index in GraphQL

For more information on ScalarDB GraphQL, see this blog post and this document.

Summary

This blog post described the recently released Scalar DB 3.8.0. This release primarily added Scalar DB Cluster, the Spring Data JDBC integration, and the GraphQL query extensions, which this blog post briefly introduced.