Comments (6)
I respectfully disagree with this statement.
It goes away from CQRS principle that you should simplify your read models to optimize your queries.
Write models, like Customer don't fit well for queries.
from equinoxproject.
I disagree. We need to protect our entities. Never receiving or returning your domain models.
from equinoxproject.
+1
from equinoxproject.
Nothing outside the AppService should know anything about the Domain.
And the Domain entities are not related to "repository/database" entities. In this sample, as we're using EF, and it's really simple demonstration, it's fine. But you should try to avoid create your Entities being concerned about persistence.
from equinoxproject.
I get very confused about this topic approach.
Because as per the traditional approach or theory wise, ViewModel should be part of User Interface Layer. At least the name says so.
View models are intended to provide information to and from views and should be specific to the application, as opposed to the general domain.
For example, what if your system with several other client types, each requiring their own ViewModel. How do you know which ViewModel a method of your application service should return?
Perhaps more appropriately, if you have a separate viewmodel for each view associated with CustomerController, should CustomerAppService have a separate method to return each viewmodel?
I think not...but that does not mean that the Domain should be returned to the Client, the Controller or another layer (Distributed Layer) should handle this.
from equinoxproject.
View models are intended to provide information to and from views and should be specific to the application, as opposed to the general domain.
Just to increase the accurate: ViewModels just provide data to the view, not otherwise. In this scenario, if the client need to send any data to the application, then this should be made via commands.
the ViewModels, from AppServices, always returns RAW data. if the client - MVC, WebAPi, etc - need to format it's exist - eg. an endpoint just need to return {id,name}, and the RAW is {id,name,address,email}. So the client should have it's own custom format, at client - WebAPI, MVC - side.
So, you're are correct, every app service call can have it's own return.
from equinoxproject.
Related Issues (20)
- 为什么只有事件保存,没有事件查询,希望通过DynamicApiControllerInfo根据Serivce 自动生成WebAPI HOT 1
- hello,where is identity context? How to use
- Exempt de Azure Function com DI HOT 2
- CRUD para um Aggregate com Child Enity HOT 2
- Some services are not able to be constructed (Error while validating the service descriptor) HOT 2
- Essa arquitetura CQRS + ES ainda é considerada válida? HOT 3
- Need migration commands to start with the projects HOT 1
- Api generating an invalid JTW signature HOT 1
- Customizar IdentityUser HOT 1
- Ajuda para teste Teste de unidade para o CommandHandler e assert do evento publicado HOT 1
- implement business rules involving multiple entities HOT 1
- When updating Identity Migration in the Equinox.UI.Web layer an error is appearing that the object of type ApplicationDbContext cannot be created HOT 8
- Relate in EquinoxContext AspNetUsers with Employee HOT 1
- Why is ApplicationDbContext.cs inside Equinox.UI.Web project? this is nonsense HOT 1
- customer history api non consistent with the name between API and Web project
- EquinoxProject is not sample of EventSourcing, but sample of audith log
- Doubt in migrations HOT 1
- update-database HOT 2
- Project still active? HOT 2
- Update DataBase HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from equinoxproject.