What I expect from some system managing storage of streams of events, intended to be used in an event-sourced system.
- ability to create streams
- ability to delete streams
- ability to use optimistic locking on stream level
- ability to write a batch of events in one stream atomically and durably
- ability to read events from one stream
- ability to read all events in the store ( the so called "$all" stream)
[|42; 42; 42|]
[42; 42; 42]
seq [42; 42; 42]
Some 42
Ok 42
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
| using System; | |
| using System.Threading; | |
| using System.Collections.Concurrent; | |
| using System.Runtime.CompilerServices; | |
| namespace CSharpStuff | |
| { | |
| // Alternative to referencing Microsoft.VisualStudio.Threading | |
| public class SingleThreadedSynchronizationContext : SynchronizationContext |
wip
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
| using System; | |
| using System.Linq; | |
| using System.Collections.Generic; | |
| namespace ZoranHorvat | |
| { | |
| public static class FunctionalCSharp | |
| { | |
| public static void Main(params string[] args) | |
| { |
pacman -Sy yay
yay -S \
dotnet-sdk \
jdk \
visual-studio-code-bin \
jetbrains-toolbox \
powershell-bin \
google-chrome \NewerOlder