SDO（服务数据对象）应该在新项目中采用吗？ [英] Should SDO (Service Data Object) be adopted in new project?

问题描述

我已经使用Midas / DataSnap在Delphi中编程了很长时间，并对此非常满意。迁移到.NET我对ADO.NET DataSet非常满意。对于CRUD应用程序，我对任何类型的ORM都非常不舒服。具有自动差异/增量处理功能的通用数据结构让我的工作变得更好，我是一名普通的数据库应用程序开发人员。

I've been programming in Delphi with Midas/DataSnap for quite long time and quite happy with it. Moving to .NET I'm more than happy with the ADO.NET DataSet. For CRUD application, I'm highly uncomfortable with any kind of ORM. Generic data-structure with automatic diff/delta handling get my job done better for me, an average database application developer.

多年前曾尝试学习Java，但却找不到类似的想法实施。我能找到的最接近的是SDO（服务数据对象）。当我看到它时，我认为它应该被广泛采用，但我错了。即使规范现在相当陈旧，我仍然很难找到很多人讨论它或广泛使用它。假设我可以在互联网上找到信息，SDO的使用非常被动。

Tried to study Java years ago, and could not find similar idea implemented. The closest I could find is SDO (Service Data Object). I thought it should be widely adopted when I saw it, but I'm wrong. Even the spec is rather old now, I still hardly find many people discuss on it or use it extensively. Assuming from information I can find on the internet, SDO usage is highly passive.

想知道它是否正在死亡？您想分享的任何SDO经验？手动DTO编码总是更好吗？

Wondering if it's dying ? Any experience in SDO you want to share ? Manual DTO coding is always better ?

推荐答案

好的。我知道了。答案是不

Ok. I see. The answer is "no"

;）

这篇关于SDO（服务数据对象）应该在新项目中采用吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！