Skip to content

Releases: EventStore/samples

Updated .NET Crypto Shredding example to .NET 6, bumped packages to the latest version

08 Dec 14:34
Compare
Choose a tag to compare
  • Updated .NET CQRS flow to .NET 6, bumped packages to the latest version
  • Moved to file-scoped namespaces.
  • Updated obsolete usage of AesManaged to Aes.Create. From: https://www.meziantou.net/cryptography-in-dotnet.htm#aes:

    "AESManaged is fully implemented in .NET, however, the implementation is not FIPS compliant. AESCryptoServiceProvider uses the Windows implementation (CryptoAPI) which is FIPS compliant. Or you can create an instance of the best available provider using AES.Create()."

Updated .NET CQRS flow to .NET 6, bumped packages to the latest version

08 Dec 14:17
Compare
Choose a tag to compare
  • Updated .NET CQRS flow to .NET 6, bumped packages to the latest version
  • Moved to file-scoped namespaces.
  • Refactored and simplified Subscription to all processing.
  • Fixed bug in the ElasticSearchProjection processing: Entity wasn't getting from the database because of missing index name.
  • Added tests for:
    • adding product item,
    • removing product item,
    • confirming shopping cart.
  • Added StreamEvent wrapper to pass event metadata (e.g. to support idempotency in the projections).
  • Updated ElasticSearchProjection to generically support idempotency.
  • Hidden generic Publish method in EventBus, as it may be getting the wrong Type (e.g. base class instead of the exact one). It's also redundant to keep it public, as the object has a method.
  • Updated SubscribeToAll logic to not fail when it wasn't possible to deserialise even.
  • Removed test report workflow, as it's flaky and not adding much value.
  • Disabled Test parallelization for API tests to not have deadlocks on starting subscription host.

See details in: #12

Samples for Protecting Sensitive Data in Event-Sourced Systems with Crypto Shredding

12 Aug 10:13
285a717
Compare
Choose a tag to compare

This sample is showing an example of using the Crypto Shredding pattern with EventStoreDB. This can be a solution for handling, e.g. European General Data Protection Regulation.

Read more in the Diego Martin article "Protecting Sensitive Data in Event-Sourced Systems with Crypto Shredding".

Description

  • shows how to Protecting Sensitive Data (e.g. for European General Data Protection Regulation) in Event-Sourced Systems.
  • shows how to use the .NET System.Security.Cryptography library with AES algorithm to encrypt and decrypt events' data.
  • uses EventStoreDB.

Other changes:

Updated the CI configuring for showing test results to:

  • not override each other if there are other changes
  • be able to be run by external PR.
    Unfortunately, that part is only to be verified once it's merged because of how GH is running the workflow triggers (the workflow file has to be on the main branch already).

See the source codes: https://github.com/EventStore/samples/tree/main/Crypto_Shredding/.NET and Pull Request.

Refactored the CQRS Flow .NET samples to not use MediatR

06 Aug 10:39
962416a
Compare
Choose a tag to compare

Refactoring of the CQRS Flow .NET example based on the feedback

  • Removed MediatR library not to have a redundant dependency from the external package (no advanced features like pipelines were used)
  • Removed marker interface for Commands, Queries and Events to reduce potential ceremony

Added sample for Event Sourcing with CQRS flow in .NET

20 Jul 12:50
Compare
Choose a tag to compare

Overview

It uses:

Write Model

Read Model

Tests

Other