Plan for .NET 8 Migration

[iammukeshm]

Here is what will come along with the .NET 8 Migration / Update.

• Upgrade to .NET 8
• Minimal APIs Only
• IHostedBackground Tasks
• Modular Monolith
• Better CLI tool to generate Modules on Demand
• Code Cleanup
• New Documentation Website
• Terraform + AWS AppRunner
• GitHub Actions + CICD Build + Test + Docker
• Test Cases
• Default InMemory Database, preferred Database will be PostgreSQL
• Vertical Slice Architecture
• Mass Transit for Modular Communication
• External Auth Provider
• SONAR Analyzers

Let me know if you need other features. PS, .NET 8 version will be released towards the final quarter.

[iammukeshm]

• Use Bogus For fake data generation.

[kallievz]

Good day @iammukeshm . Hope you are well.

Any ETA for the .Net 8 Migration, looking forward to this update...

[MohAshour]

appreciate to update blazor-wasm-boilerplate to .NET8 too.

[nguyenducmanh2106]

when will you continue to complete the dotnet-microservices-boilerplate repository?

[darkfame]

Definitely interested in seeing your VSA implementation. Please cover adding additional features/slices.

[sooneeatwork]

VSA and cross module communication, if some operation involve code from 2 module, how is the communication looks like

[iammukeshm]

• No Module will be able to access the code of the other module directly.
• Maybe have interfaces and create a runtime dependency.
• Even better, add a mass transit broker to communicate.

What would you do?

[sooneeatwork]

message broker is good for async operation, what about synchronous operation? my solution for synchronous operation now is create a shared class library and declare interface in that library, all module will be reference the shared class library to access/implement the interface for cross module need,

[timsar2]

What about replacing Mediator with Wolverine?

Wolverine is The Next Generation .NET Mediator and Message Bus.

[Sharafudeen]

Following can be consider when upgrading the current version,

1. Upgrade should not affect major changes in the current version of FullStackHero WebApi.
2. Default database will be SQLite since it is cross-platform
3. Module/Feature can be easily managed
4. Permission can be easily managed but not "hard coded" in the code level
5. Tenant, Edition, Feature can be introduce to prefer SaaS based applications
6. Source Generator for adding new or updating existing Module/Feature
7. Vector Database can be supported. For example, milvus, weaviate

[punkouter25]

going from CLEAN to VERTICAL is a massive change isnt it ? I been looking at both recently and it does seem CLEAN is overkill

[JonasDev17]

Why Minimal APIs only?

[maxiar]

Why mantaint two project web api and microservice boilerplates…. if a microservice can be containt a webapi perfectly…. and also you need to upgrade the blazor ui to be compatible with webapi and microservice.. I think that is too job for you… May be we need an integral plan to unified all boirplates in a modular design… what do the communkty think?

Thanks in advanced!

[maxiar]

@iammukeshm What do you think about this? I think that It sounds coherent and has a long-term vision that is easy to maintain.

[maxiar]

Add support for modularize/reuse the "common" libraries, for example if I've two API services with 2 tables different eachs.
I need to "Copy/Paste" the Infraestructure/Application "Copy/Paste" the all infraestructure layer, because the ApplicationDb, Identity, Audit are very couped, I can't disable auditing or identity easyly.
Usually a project has multples webapis services with the same infraesctructure/application.common (database, cache, serialization, identity, loggings) may be the common layer can be shared by nuget lib..
A HostApi must be a separated webapiservices from identityservices and hangfire scheduler services, all sharing the same infraestructure layers configuring by DI the custom configuration.

Something like that is covered in the "Modular Monolith" net8 feature?

It's more like a microservices arch. It's similar to the above question, a webapi can be inside a microservices, and all microservices can be shared/or not the same infraestructure layers or common infraestructure services like loggin, cache, identity, auditing, etc...

How can I help with the net8 upgrade on this way..?

[JonasDev17]

Add support for multiple ways to authenticate simultaneously like AzureAD and JWT.

Previously it was "either JWT or AzureAD" and just chaining them does not work.

[iang0ld]

Mukesh do you have any timeline or Targeted Release Date for this new .NET 8 version on BlazorHero?

[kallievz]

Awesome, not too sure about minimal api's though.
Hangfire expansion to allow for processes by named custom queue,
Background workers using hangfire without using tenant, eg. global maintenance jobs across all tenants. (Index maninenace , file system monitors)
Per tenant settings. Same table structure, different validations, soft settable. Eg Account number lenghts, account number padding per tenant.
Option to add Logo for Tenant, for branding different tenants with their own logo.
Like BlazorHero, option to communicate among each other.
Ability to switch dynamically between auth methods based sequence LDAP, AD, JWT

[timsar2]

what about SignalR? becuase minimal api does not support signalr, so how we can implement notification module? does it need to be aot dotnet?

[wtmaxim]

what about SignalR? becuase minimal api does not support signalr, so how we can implement notification module? does it need to be aot dotnet?

You are right, minimal APIs in .NET do not directly support SignalR. Here is the link to the PR where we have started working on this integration: #956 . Feel free to review and provide your feedback.