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: README.md
+3-10Lines changed: 3 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -189,16 +189,9 @@ for a more detailed overview of where we're at and where we see things going!
189
189
190
190
# priorities
191
191
192
-
* rework the transaction API to eliminate surprises and limitations
193
-
* reduce space and memory usage
194
-
* the 1.0.0 release date is imminent! just putting the final touches on, while performing intensive testing
195
-
* combine merge operators with subscribers in a way that plays nicely with transactions
196
-
* typed trees for low-friction serialization
197
-
* replication support for both strongly and eventually consistent systems
198
-
* continue to improve testing and make certain bug classes impossible through construction
199
-
* continue to optimize the hell out of everything
200
-
* continue to improve documentation and examples
201
-
* continue to reduce compilation latency
192
+
1. A full rewrite of sled's storage subsystem is happening on a modular basis as part of the [komora project](https://github.com/komora-io), in particular the marble storage engine. This will dramatically lower both the disk space usage (space amplification) and garbage collection overhead (write amplification) of sled.
193
+
2. The memory layout of tree nodes is being completely rewritten to reduce fragmentation and eliminate serialization costs.
194
+
3. The merge operator feature will change into a trigger feature that resembles traditional database triggers, allowing state to be modified as part of the same atomic writebatch that triggered it for retaining serializability with reactive semantics.
0 commit comments