scalardb | Universal transaction manager | Database library

I'd like to estimate the costs of Azure CosmosDB on Scalar DB. CosmosDB requires the following parameters. But these parameters are not ScalarDB parameters.

• API
• Number of Regions
• Multi-region writes
• Default consistency
• Indexing policy
• Total data stored in transactional store
• Use Analyltical Store
• Workload mode
• Item Size
• Number of properties
• Point reads/sec
• Creates/sec
• Updates/sec
• Deletes/sec
• Queries/sec
• Average RU charge per query

So, should we set which configuration and can we above parameters map to Scalar DB parameters?

I confirm the following questions. About Configuration

• API -> Cassandra
• Number of Regions -> If we need to write into multi-region, set over 2.
• Multi-region writes -> If the multi-regions is over 2, set to "Enabled"
• Default consistency -> Strong. But CosmosDB could satisfy transactions across multi-partitions. It is covered by Scalar DB.

About API calls Scalar DB APIs vs ComosDB APIs

• Put: Insert without condition => createItem()
• Put: Insert with condition => readItem() -> not exists -> createItem()
• Put: Update with condition => readItem() -> if conditions are satisfied -> merge columns -> replaceItem()
• Get -> readItem()
• Delete without condition => deleteItem()
• Delete with condition => readItem() -> if conditions are satisfied -> deleteItem()
• Scan => container.queryItems()

I think ScalarDB has some operations before the above operations which check the transaction state. So, Does Scalar DB require more ComosDB API Calls?

In ScalarDB, the library that add ACID functionality to Cassandra, I am getting the following error

In ScalarDB, the library which provides ACID functionality on top of Cassandra, what does Get return if clustering key is not present and there are multiple rows in the database for same partition key?

I am using scalardb which provides ACID funcationality on top of Cassandra. I want t unit test a method (add) which should add a new row if it is not a duplicate.

I am using ScalarDB. It provides ACID capabilities over Cassandra. - https://scalar-labs.github.io/scalardb/javadoc/

ScalarDB is Java based and I am using it in Scala code

The way to insert a value in Cassandra using Scalardb is to call Put method. Eg.

I am using ScalarDB to add ACID support in Cassandra application. What happens if I start a Transaction but don't commit it. Could there be any adverse effects of it?

Eg.

I am using ScalarDB which provides ACID functionality on Cassandra. While deleting a record, I am getting com.scalar.db.exception.transaction.InvalidUsageException: the record to be deleted must be existing and read beforehand exception.

I am deleting entries from several tables (thus using Scalar to provide Atomocity). I created a DistributedTransaction at the start and then started deleting the entries.

This question is part-Cassandra and part ScalarDB. I am using ScalarDB which provide ACID support on top of Cassandra. The library seem to be working well! Unfortunately, ScalarDB doesn't support pagination though so I have to implement it in the application.

Consider this scenario in which P is primary key, C is clustering key and E is other data within the partition

I am using ScalarDB which adds ACID support in Cassandra. Referring to the documentation, how is PutIf different from PutIfExists and PutIfNotExists?

I suppose PutIfExists is like an update PutIfNotExists is like a new addition

What is PutIf? When to use it?