Clean Architecture - Blazor WebAssembly - How To Use Command Query Responsibility Segregation - CQRS

Clean Architecture - Blazor WebAssembly - How To Use Command Query Responsibility Segregation - CQRS Pattern .Net 6
Video ini membahas tentang implementasi clean architecture di blazor webassembly.
Video Detail :
0:00 Previously on froger devs
6:45 Install MediatR
16:25 Implement CQRS Pattern
34:00 Create BaseControllerApi
47:00 Sample CRUD Function - in memory
Video Sebelumnya :
- Clean Architecture • Blazor c# .net 6 | Cle...
- Clean Architecture Blazor WebAssembly - Separate Client from Server • Clean Architecture Bla...
Video Lainnya:
- Blazor Server VS Blazor WebAssembly (wasm) • Blazor dotNet 6 C# | B...
- Migrate From .Net 5 to .Net 6 • Migrate From .Net 5 to...
- Clean Architecture • Blazor c# .net 6 | Cle...
- Clean Architecture Blazor WebAssembly - Separate Client from Server • Clean Architecture Bla...

[@davidsantacruz7195]

Good video, thanks. What do you think about using the domain (entities, aggregates, enums, logic, etc.) into the Blazor WebAssembly client? Or we only can share DTOs between Backend and Frontend?

[@FrogerDevs]

Hi David,
"Never use the Domain Layer inside the Presentation Layer",
for example, in Ordering Application: the Domain Layer only focuses on entities to store (table) orders and update stock (table) items, but what the presentation layer (Blazor wasm) needs is a more meaningful response, which is a combination of many entities, the Presentation Layer is not needed to process the response data again leave the task to the backend, it will make your application more efficient.
The next reason is that Blazor Wasm is a Single-Page Application (SPA) like reactjs and vue, so when your company wants to change to another framework, or another library in the future, just change your Presentation Layer, not the entire application.
With this concept, your application is scalable, and if your current application is still monolithic and you want to move to microservices in the future, it is easy to divide your features into microservices.
So in conclusion, keep it using DTOs for communication between the frontend and backend.

[@davidsantacruz7195]

​@@FrogerDevs thanks for your answer. I agree about using DTOs for communication.