Singlestore as OLTP system

1

Hi Team,
As I understand that singlestore is ACID compliant and with READ COMMITTED isolation level which will leave data in Inconsistency state, we would not want to control the data consistency thru programming either by issuing FOR UPDATE or BEGIN TRANSCTION mode. With the current Isolation level as READ COMMITTED we are not able to suggest to use SINGLESTORE for OLTP applications. If we get the feature of DB with isolation level of what other ACID compliance databases viz . DB2, ORACLE, COCKROACH DB etc…, we would like to explore it for our client requirements.

I really appreciate if could you share the right info on whether any of the current/future version(s) of SINGLESTORE DB is supporting all the properties of ACID that can be used for OLTP applications.
Thank you
with regards,
Prathap Reddy G

2

Hi Prathap,

SingleStore can handle transactional workloads. You’re right that READ COMMITTED is our default isolation mode. Based on our multi-version concurrency control, readers and writers don’t block each other in this mode. We support transactions, HA, DR, point-in-time recovery, and if you use SELECT… FOR UPDATE you can control isolation to to meet needs of mission-critical financial OLTP. We support two-phase commit by default for atomic transactions on sharded (multi-node) databases.

You said you don’t want to try FOR UPDATE. Why’s that?

Eric