布局实体模型的最佳实践有哪些？
最初，我们希望将数据库清楚地分成逻辑上独立的实体。然而，我们与域服务类遇到了一些冲突。
现在看来，处理复杂数据库模型的最佳方法是将所有表/存储过程/视图加载到一个实体模型中，然后通过域服务类/存储库类分离功能。
想法？
您布置实体的架构方法是什么？
将所有内容都集中在一个模型中是否有性能优缺点？
Initially we wanted to clearly separate our database into logically separated entities. However we ran into several conflicts with our domain service classes.
Now it seems that the best approach for working with complex database models is to load all tables/stored procedures/views into one entity model and then separating the functionality through the domain service classes/repository classes.
Thoughts ?
What are your architecture approaches for laying out entities ?
Also are there any performance pros/cons of having everything in one model ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
也许将模型分成几个图表是个好主意？
Entity Developer 的最新版本提供了创建包含模型中不同实体的独立图表的机会。
Maybe separating model into several diagrams is a good idea?
The latest build of Entity Developer gives an opportunity to create independent diagrams containing different entities from the model.