antoniofalcaojr/eventualshop

A state-of-the-art distributed system using Reactive DDD as uncertainty modeling, Event Storming as subdomain decomposition, Event Sourcing as an eventual persistence mechanism, CQRS, Async Projections, Microservices for individual deployable units, Event-driven Architecture for efficient integration, and Clean Architecture as domain-centric design

@AntonioFalcaoJr 👋

Hands-on Software Solutions Architect, BSc & MSc student in Computer Science,
experienced in Reactive DDD, Event Sourcing, CQRS, and Distributed Systems
within the .NET ecosystem

eventualshop's Issues

Refact Communication based on Catalog

Update Tech stack on readme

Improvement CorrelationId between context - web - api

Splite the huge Docker Compose into multiple files

Is your feature request related to a problem? Please describe.
The considerable file for docker-compose.yml break the single responsibility principle

Describe the solution you'd like
I suggest creating multiples files for docker-compose

Executing a new strategy is simple:

docker-compose -f docker-compose.db.yml \
  -f docker-compose.api-services.yml \
  -f docker-compose.backend.yml \
  -f docker-compose.frontend.yml \
  -f docker-compose.gateway.yml \
  up -d`

Projections to DB

Hi Guys,
thanx for the work done in the code, i would like to know if its possible to have Projections point to NoSQL and SQL server,
will it be a compromise if we have have SQL server.. please advise on this regard
M

Refact Shopping Cart based on Catalog

The use C4 diagrams.

Is your feature request related to a problem? Please describe.
After reading completely I see an opportunity to use c4 diagrams to pattern the project and create reactive documentation, today known the architecture changed since the first release.

Describe the solution you'd like
My suggestion is to use the c4sharp, an awesome library c# forecast to create diagrams.

https://github.com/8T4/c4sharp

Refact Order based on Catalog

Bug in the Queries.cs

I have also picked up a bug in the Queries.cs

please advise if i allowed to do a pull request and make those change...

M

Adjust Serializers on MessageBus and EventBus layers

Adjust Serializers on MessageBus and EventBus layers

Objectives:

• To change the MessageBroker infrastructure layers (MessageBus and EventBus) to use System.Text.Json instead Newtonsoft.Json

Response envelop gRPC to HTTP

Refact Warehouse based on Catalog

Primitive obession with Money

Refact Payment based on Catalog

Refact Account based on Catalog

Improvement observability with filebeat

The main goal: each container std::out logs and file beat inside container publish this information for elastic search and show on Kibana.

Refact Identity based on Catalog