v1.1.0

• Use test-container for integration-test
• Improvement test base

More details: PR #66

v1.0.9

• Add test-container for RabbitMq in test-base
• Refactor all tests

More details: PR #65

v1.0.8

• Add versioning to feature folder structure

More details: PR #55

v1.0.7

• Change grpc services from magic-onion to grpc-dotnet

More details: PR #51

v1.0.6

• Add sample for multi-consumers for user-created
• Fix bug in serilog console

I added a sample for RegisterNewUser endpoint and after that publish an event user-created and consume this event in multiple consumers (Flight-Services and Passenger-Services).

More details: PR #43

v1.0.5

• Move PersistMessageDB to Separate DB.
• Fix bug for calling Projection in Event Store
• Fix bug for store duplicate data in PersistMessageProcessor

More details: PR #36

v1.0.4

• After saving data in write side, I save a Internal Command record in my Persist Messages storage (like something we do in outbox pattern) and after committing transaction in write side, trigger our command handler in read side and this handler could save their read models in our MongoDB database.

More details: PR #32

v1.0.3

• Using Inbox Pattern to handle incoming messages (e.g. from a queue) for unique processing of a single message only once (even with executing multiple time).

More details: PR #19

v1.0.2

• Using Outbox Pattern for ensuring that a message was sent (e.g. to a queue) successfully at least once. With this pattern, instead of directly publishing a message to the queue, We put it in the temporary storage (e.g. database table) for preventing missing any message and some retry mechanism in any failure (At-least-once Delivery).
• Using Internal Command Processor For syncing Read Side and Write Side without event sourcing in MongoDB or other read database.

More details in this PR #16

v1.0.1

• Add Health Check for SqlServer, Rabbitmq, Masstransit, Issue #10

More details in this PR #13