eShopOnContainers VS sqlx

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?

What exactly are you missing? I haven't really written "boring corporate backend stuff" in a few years but something like sqlx provides everything I've ever needed there.

Badges are the little rectangles you typically see at the top of a crate's README: https://github.com/launchbadge/sqlx/blob/main/README.md

SQLX has entered the chat [1].

[1] https://github.com/launchbadge/sqlx

Database : SqLite (using sqlx).

The current (well, removed) MSSQL sqlx driver also doesn't support encrypted connections (https://github.com/launchbadge/sqlx/issues/1552), so it might work locally on an unnamed instance but not over the network until they add in the newer driver (which will be closed source but for an OSS project you should be able to request a free license I think)

I'm considering making my own wrapper over lower-level database drivers. There are a lot of features in sqlx that I don't need, and the latest version seems to have removed useful data structures that SQLPage is using. It also removed support for SQL Server.

add Ed25519 to AuthPlugin enum on https://github.com/launchbadge/sqlx/blob/061fdcabd72896d9bc3abb4ea4af6712a04bc0a8/sqlx-core/src/mysql/connection/auth.rs and implement them using these crates: