Sync Framework 2.1 - 已停产??? [英] Sync Framework 2.1 - Discontinued ???

问题描述

有一个案例与Microsoft就Sync Framework 2.1中的错误打开了一个案例，类似于此处讨论的案例：

Had a case opened with Microsoft regarding to a bug in Sync Framework 2.1, similar to the one discussed here:

http://social.msdn.microsoft.com/Forums/en-US/syncdevdiscussions/thread/08bbeec4-5a4e-4034-a600-3fe68557e94a

请求修补程序或未来开发计划的更新。得到了这样的答复：

是的，我们确认这个问题出现在SyncFx 2.1中，并且没有计划在框架中解决它因为该技术的未来发展将停止。  我们计划在
SQL Azure Data Sync CTP3 CU5中解决这个问题，这是下一个版本。  

HUH ???这是否意味着Sync Framework正在停止使用，只有Azure Data Sync Agent才会保留，而开发人员无法使用实际的API？任何熟悉该领域微软路线图的b $ b b，请澄清声明。 

基本上，我们希望有一个可靠的框架，可用于开发自定义同步服务，该服务将来自多个客户端数据库的数据与Azure"母亲"同步。数据库。在相关的微软技术范围内，它仍然是可靠的主张，还是我们必须考虑编写自己的同步机制？  

Essentially, we are looking to have a reliable framework which can be used to develop custom sync services which sync data from multiple client databases with the Azure "mother" database. Is it still tenable proposition within the scope of the related Microsoft technologies, or we got to consider writing our own sync mechanism?  

混音器

推荐答案

Hi Mixer，

Hi Mixer,

我们是正在处理负时间戳值问题，并将针对此问题发布Sync Framework 2.1的修补程序。 我们仍然致力于确保Sync Framework能够满足开发人员根据SyncFx编写应用程序
的需求。 我们现在正在计划制定一个为期18个月的Sync Framework路线图。 如果您有特定的功能请求，我们很乐意听取您的意见。

We are in process of addressing the negative timestamp value issue and will release a hotfix of Sync Framework 2.1 for this issue.  We remain committed to make sure that Sync Framework will serve the needs of developers writing applications based on SyncFx.  We are now in the planning process of putting together a 18-month roadmap for Sync Framework.  If you have specific feature requests, we would love to hear from you.

对于从多个本地SQL Server数据库同步到中心SQL Azure数据库的特定方案，我们认为数据同步服务应该能够很好地满足基本需求，而无需编写代码和最短的部署时间;但是，如果
涉及复杂的业务逻辑（例如自定义冲突解决策略），Data Sync Service无法处理，那么Sync Framework仍然是推荐的（尽管成本更高）方法。

For your specific scenario of syncing from multiple on-prem SQL Server databases to the hub SQL Azure database, we believe Data Sync Service should be well-positioned to serve the basic needs without writing code and minimal time to deploy; however, if there are complex business logic involved (e.g. custom conflict resolution policies) that cannot be handled by Data Sync Service, then Sync Framework is still the recommended (albeit more costly) approach.

我希望这能解决你的问题。

I hope this addresses your concern.

Shirley Wang

Shirley Wang

这篇关于Sync Framework 2.1 - 已停产???的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！