Added event store session to SQLite event store - #313
Merged
Conversation
That ensures that connection is reused during command handling and that operations are serialized not causing concurrency issues.
oskardudycz
force-pushed
the
sqlite_session_storage_handling
branch
from
March 2, 2026 13:11
3fe6ddf to
c3d6c70
Compare
Collaborator
Author
|
Benchmark results on my local (not so fast) box: Reading events 5,826 ops/sec
Aggregating stream 7,702 ops/sec
Appending events 1,486 ops/sec
Command handling 447 ops/sec
1000 sequential appends 1,132 ops/sec
1000 sequential command handling 198 ops/sec
1000 concurrent appends to unique streams 5,678 ops/sec
1000 concurrent command handling on unique streams 2,376 ops/sec |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

That ensures the connection is reused during command handling and that operations are serialised, preventing concurrency issues.
Added execution guards to make execution handling easier based on the task processor.
@SamHatoum @davecosec @LuccaHellriegel FYI