Scalar Inc. (Headquarters: Shinjuku-ku, Tokyo; CEO and COO: Wataru Fukatsu; CEO and CTO: Hiroyuki Yamada) has released the new version 3.2 of ScalarDB, a general-purpose transaction manager. In ScalarDB 3.2, we implemented a transaction management function for microservices that easily maintains consistency between databases in microservices (*1). By providing this function, Scalar aims to significantly reduce the burden on application developers in microservice-based applications.
Scalar has developed ScalarDB as a transaction management mechanism that runs on a variety of databases. We implemented the function in ScalarDB and released it as version 3.2.
In order to realize microservices in database applications, it is necessary to maintain consistency between databases. There were methods such as commit), but there were problems that implementation was difficult or it was not always easy to achieve high availability. ScalarDB 3.2 has implemented a transaction management function for 2PC-based microservices to solve those issues.
This enhancement enables application developers to develop highly available microservices-based database applications without complex implementations. In addition, since this function operates on all databases supported by ScalarDB, transactions across NoSQL such as RDB, Cassandra, Amazon DynamoDB, Azure CosmosDB, etc., as well as between RDBs (MySQL, PostgreSQL, Oracle Database) It is possible.
For details on the transaction function for microservices, please refer to the following site.