[Brainstorm] Software architecture

[thangchung]

Would like to see some kind of dynamic field for CMS with multi-tenancy architecture like https://github.com/arduosoft/RawCMS/blob/master/RawCMS.Library/Schema/Field.cs

• Lightweight approach for CRUD at https://github.com/the-linck/Generic-Entity-MVC-CRUD/blob/master/Controller/CrudController.cs (more than 50% actions in application is CRUD).

• https://github.com/asc-lab/dotnet-cqrs-intro => 5 types of CQRS

• https://github.com/asc-lab/dotnetcore-microservices-poc => good with Marten for event sourcing and search service

• https://github.com/BrighterCommand/Darker ==> has Retry/Fallback policy

• https://github.com/oskardudycz/EventSourcing.NetCore -> Event Sourcing using Marten

• https://github.com/ddd-by-examples/factory

• https://github.com/GaProgMan/OnionArch
• https://github.com/ardalis/CleanArchitecture
• https://github.com/jbogard/AdventureWorksCosmos
• https://github.com/DavidCBerry13/FoodTruckNationApi
• Good wrap up of repository at https://github.com/sogustavo/sidekick/blob/master/EntityRepository/Repository.cs
• https://github.com/FanrayMedia/Fanray => full blog plugin application
• https://github.com/AjuPrince/Aju.Carefree

Multi-tenancy:

• https://github.com/abpframework/abp/tree/dev/framework/src/Volo.Abp.MultiTenancy or search the repo at https://github.com/abpframework/abp/search?q=Tenant&unscoped_q=Tenant
• https://github.com/aliakseiherman/eixample and https://github.com/aliakseiherman/eixample_webapi2
• https://github.com/Boriszn/DeviceManager.Api
• https://github.com/hakeemoriola/MultiTenancyServer.MongoDb

Cloud native book: https://github.com/ardalis/azure-cloud-native-book/blob/master/architecting-cloud-native-dotnet-apps-for-azure/azure-platform-resiliency.md

Pub/Sub:

• at-most-once delivery: means that for each message handed to the mechanism, that message is delivered zero or one times; in more casual terms it means that messages may be lost.
• at-least-once delivery: means that for each message handed to the mechanism potentially multiple attempts are made at delivering it, such that at least one succeeds; again, in more casual terms this means that messages may be duplicated but not lost.
• exactly-once delivery: means that for each message handed to the mechanism exactly one delivery is made to the recipient; the message can neither be lost nor duplicated.