You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: versioned_docs/version-3.13/roadmap.mdx
+1-6Lines changed: 1 addition & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ If you have a feature request or want to prioritize feature development, please
46
46
47
47
-**Addition of read-committed isolation**
48
48
- Users will be able to run transactions with a read-committed isolation to achieve better performance for applications that do not require strong correctness.
49
-
-**One-phase commit optimization for a single relational database**
49
+
-**One-phase commit optimization**
50
50
- Users will be able to run a transaction more efficiently by using one-phase commit if the operations of the transaction are all applied to a single database or a single partition.
51
51
-**Optimization for multiple write operations per database**
52
52
- Users will be able to run transactions more efficiently with a batch preparation and commitment if there are multiple write operations for a database.
@@ -82,11 +82,6 @@ If you have a feature request or want to prioritize feature development, please
82
82
-**Enabling of read operations during a paused duration**
83
83
- Users will be able to issue read operations even during a paused duration so that users can still read data while taking backups.
84
84
85
-
#### Performance
86
-
87
-
-**One-phase commit optimization**
88
-
- Users will experience faster execution for simple transactions that write to a single partition. ScalarDB will omit the prepare-record and commit-state phases without sacrificing correctness if a transaction updates only one partition by exploiting the single-partition linearizable operations of the underlying databases.
0 commit comments