Ruben Bartelink
Ruben Bartelink
There's a note regarding avoidance of `TaskCreationOptions.LongRunning`: >💡 NOTE:`Task.Factory.StartNew` has an option `TaskCreationOptions.LongRunning` that under the covers creates a new thread and returns a Task that represents the execution. Using...
This ports `Sample/EventStoreDB/Simple/ECommerce/ShoppingCarts` to a) F# b) Equinox There are some variations introduced as part of the port: - In general, [idiomatic Equinox modules](https://github.com/jet/dotnet-templates#aggregate-module) tries to encapsulate the contracts and...
See #1626 for some context as to the sort of conflict resolution scenario I'm attempting to implement TL;DR I have a conflict resolution loop in reaction to `WrongVersionException`, but I...
Works on CI, but not in Rider latest or 2022.2 EAP 1
Breaking change/things that are ugly queue: - Add OpenTelemetry integration - `CosmosStore`: will shift to [using `Azure.Cosmos` when that happens](https://github.com/Azure/azure-cosmos-dotnet-v3/discussions/2601). When that work might happen is subject to change. Here's...
The default CosmosDb consistency level (Session) involves round-tripping a [`SessionToken` value](https://docs.microsoft.com/en-us/azure/cosmos-db/how-to-manage-consistency#utilize-session-tokens) between the outcome of a given request through to its successors(s) in order to achieve Read-Your-Writes. Necessary steps off...
The current indexing policy in the 2.x series was the result of trying pretty much every combination of individual and composite indexes. I was definitely frustrated by some obvious composite...
Provides a `Equinox.EventStore.AccessStrategy.CustomOrigin` which would be useful in the context of https://github.com/jet/dotnet-templates/pull/40 to enable a custom lookback on a long-running stream (without employing the snapshots strategy). 🤔 Still mulling over...
Takes `master` (which uses Cosmos SDK v3 (`Microsoft.Azure.Cosmos`) + makes it use V4 (`Azure.Cosmos`) The diffs are fairly large between current `master` and the base of this PR; main reason...
This PR exposes a `SessionToken` on `Equinox.Core.ISyncState`, which enables logic in a `Service` to access that (along with the `Version` plumbed in #194) via the `QueryEx` and `TransactAsyncEx` APIs. More...