ORM和SOA在.NET世界 [英] ORM and SOA in the .NET world
问题描述
从我的经验用于.NET的主要ORM框架（ NHibernate的，的 LinqToSql ，的实体框架）效果最好时，他们跟踪装载的对象。这工作正常进行简单的客户端 - 服务器应用程序，但在面向Archtitecture服务与使用Web服务的三个或更多层架构的时候，这是不可能的。最终，通过编写大量的code做跟踪自己也可以做，但不是ORM应该简化了数据库的访问？
From my experience the major ORM frameworks for .NET (NHibernate, LinqToSql, Entity Framework) work best when they keep track of loaded objects. This works fine for simple client-server applications, but when using three- or more tier architecture with Web Services in a Service Oriented Archtitecture, this is not possible. Eventually, by writing a lot of code to do the tracking yourself it could be done, but isn't ORM supposed to simplify DB access?
是在面向服务的架构良好的使用ORM在所有的想法？
Is the idea to use ORM in service oriented architecture good at all?
推荐答案
LLBLGEN专业版具有改变跟踪的实体内。这意味着，你可以使用prefetch路径（每个图节点，这样一个查询）从数据库中获取的曲线，它通过网线给客户端序列化，改变它那里，它发回，并直接在图形保存所有变化跟踪是实体内（与序列化的XML作为紧凑型自定义元素内）。
LLBLGen Pro has change tracking inside the entities. This means that you can fetch a graph from the database using prefetch paths (so one query per graph node) and serialize it over the wire to the client, change it there, send it back and directly save the graph as all change tracking is inside the entities (and is serialized inside the XML as compact custom elements).
免责声明：我LLBLGEN亲的首席开发人员
Disclaimer: I'm the lead developer of llblgen pro.
这篇关于ORM和SOA在.NET世界的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
