raytha VS m-r

Raytha is a production level CMS and starter kit built on top of CleanArchitecture template so its a more full fledged example .

You can see how this project does it: https://github.com/RaythaHQ/raytha/tree/main/src

I maintain an open source .NET CMS and it uses Entity Framework for 90% of the application, but the remaining 10% uses Dapper with SQL Server's JSON functionality. I received a pull request for potential support for MySQL, but it does not address that JSON functionality issue. I think it may be worth it to spend some time to support both SQL Server and MySQL or Postgres.

Github: https://github.com/raythahq/raytha

However, SQL Server has recently greatly improved their support for JSON columns though they still have a ways to go in my opinion. The trade off here is that to get the full power of it, you cannot use EF Core. You have to write the raw SQL queries and use something like Dapper. https://github.com/RaythaHQ/raytha is an example of a project does this.

You may want to check out https://github.com/raythahq/raytha. It's a starter template for .NET applications that uses established patterns that are popular in large scale applications. It might be a good idea to practice on it.

Here's the simplest implementation from the inventor himself: https://github.com/gregoryyoung/m-r

https://github.com/gregoryyoung/m-r from the man himself. I know it says CQRS, but you can't do event sourcing without CQRS. Just as long as this is just for educational purposes. Event sourcing is, as cookie monster says, a sometimes food.