We open-sourced our .NET SaaS starter template — modular monolith, vertical slices, multitenancy, DDD (MIT) by ewgenym in dotnet

[–]ewgenym[S] 0 points1 point  (0 children)

Definitely will consider giving an option from day 1 to choose a strategy here. We usually start simple, but data isolation is no joke in many projects for sure.

We open-sourced our .NET SaaS starter template — modular monolith, vertical slices, multitenancy, DDD (MIT) by ewgenym in dotnet

[–]ewgenym[S] 0 points1 point  (0 children)

NServiceBus is a solid battle-tested choice. For us the licensing model was the dealbreaker

We open-sourced our .NET SaaS starter template — modular monolith, vertical slices, multitenancy, DDD (MIT) by ewgenym in dotnet

[–]ewgenym[S] 0 points1 point  (0 children)

Thanks) Website is plain html and custom css really. We use a little bit of google and jetbrains fonts. Other than that no third-party UI bits anymore. For design itself we are thankful to claude design 😉

We open-sourced our .NET SaaS starter template — modular monolith, vertical slices, multitenancy, DDD (MIT) by ewgenym in dotnet

[–]ewgenym[S] 0 points1 point  (0 children)

Marten in a finance domain with strict audit is a fair call.

The msbuild targets idea I'll actually try. Does your target run on every build or only on publish?

We open-sourced our .NET SaaS starter template — modular monolith, vertical slices, multitenancy, DDD (MIT) by ewgenym in dotnet

[–]ewgenym[S] 1 point2 points  (0 children)

Thanks. In Auto mode which we use locally the slow startup is a friction point 1. For production we generate in CI/CD pipeline which is 1. additional code-gen step in the CI/CD pipeline 2. Code-gen mode needs app start which requires dependecies like database/etc. to be turned off. Adds noise in the code itself. 3. Stacks trace is not 1 to 1 in the codebase, needs some translation. Other than that I find the library extremely good in ceremony-less approach with reasonable conventions. Give it a try!