eShopOnContainers VS system-design-primer

The eShopOnContainers is pretty popular, have you seen it yet? https://github.com/dotnet-architecture/eShopOnContainers

so I was exploring eShopOnContainers a little bit, more specifically the messages queues part and it made me wonder how is it possible to ensure data consistency across microservices when using them. If I'm not mistaken this isn't even shown in the eShopOnContainers examples.

For an example of an aggregate if you're unfamiliar - https://github.com/dotnet-architecture/eShopOnContainers/blob/3169a933447f1013c069e2cad2805c5de1ce9fbf/src/Services/Ordering/Ordering.Domain/AggregatesModel/OrderAggregate/Order.cs

You can check out eShopOnContainers as a reference architecture if you want, but (assuming this is meant to be somewhat of an ad hoc solution rather than a paragon of software engineering) I'd minimize the number of deployable assemblies (1 + tests if possible) and avoid Docker, again unless you have a specific reason to use it.

For K8s, it has a whole directory with deployment scripts. https://github.com/dotnet-architecture/eShopOnContainers/tree/dev/deploy/k8s

Checked the eshop on containers which uses EF for writes with DDD. Queries uses Dapper with raw sql. https://github.com/dotnet-architecture/eShopOnContainers/blob/dev/src/Services/Ordering/Ordering.API/Application/Queries/OrderQueries.cs

Maybe Microsoft’s eShopOnContainers reference system?

✅ donnemartin/system-design-primer: https://github.com/donnemartin/system-design-primer

View on GitHub

I've been giving interviews for past couple of months and this github repo has helped me so much for system design perspective and I can see myself excelling at interviews. - https://github.com/donnemartin/system-design-primer

You'll be on opiod's probably the first 1-2 days, so sleeping should be fine. Everything will be allright, don't worry too much. Just use the time now to prepare for the time after, make sure you go through post-surgery-essentials thread. Once you are out of the OR you won't have the energy to think about those details, so make sure you take that prep serious.

Tooling isn’t architecture. Figure out what you need to handle both personas and volume/throughput and then lay out the capabilities you’ll need. As you lay out points of ingress, egress, consumption you can start to lay out sequences(think in persona and sequence diagrams to express interactions between services). Lastly, evaluate tools that offer some of these capabilities and weigh the trade-offs (there are always trade-offs: https://github.com/donnemartin/system-design-primer).

[1] https://github.com/donnemartin/system-design-primer [2] https://www.teamblind.com/post/My-Approach-to-System-Design-V4SJARdx