eShopOnContainers VS PeakLimsApiSample

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?

https://github.com/pdevito3/PeakLimsApi valuable sample, recommend

If you’re having trouble getting started backend wise, I made a tool that can scaffold some boilerplate for you. You can also check out projects like Jason or ardalis’s clean architecture projects. Here’s one that’s a little dated but still good.

If you’re interested, something like this is a more built out project I built a while back. It’s not done and I’d change several things looking back, but it gives you an idea. If you want to try something similar you can scaffold out an api with this tool, but there are other good projects you can reference as well!

Currency was another you mentioned. That sounds more like a value object like this (this is an example ddd project overall too if you want to check it out — here’s another) that you could replace your primitives with.

Here’s a few: - complex domain driven example using vertical slice - another DDD example - clean architecture template by Jason taylor - clean architecture template by ardalis