托管服务引擎（MSE）路线图 [英] Managed Services Engine (MSE) Roadmap

问题描述

有人能够指出该项目（受管服务引擎）是否已被放弃？

Is anyone able to indicate if this project (Managed Service Engine) has been abandoned?

我需要决定是否将此作为我的企业服务虚拟化计划的一部分。目前，我看到许多来自Microsoft的竞争解决方案，例如AppFabric Server，Olso和自定义WCF，但没有一个提供像MSE支持那样的治理级别。

I need to make a decision on whether or not to use this as part of my enterprises service virtualisation plans. I see a number of competing solutions from Microsoft at the moment like AppFabric Server, Olso and custom WCF, but none offer the level of governance like the MSE enables.

我不想被称为统一解决方案出现后的一年内选择不佳的人。

I do not want to be known as the guy that choose poorly in a year from now when the unified solution appears.

如果不再开发MSE，您是否认为通过采用它，内置的解决方案是否可以移植到替代产品中？

If MSE is no longer under development, do you think that by adopting it anyway, solutions built in it will be portable to the replacement product?

推荐答案

我最近在一个研究使用MSE的项目中。调查于2011年第一季度进行。在与Microsoft代表和MSE团队的前成员交谈之后，我们发现Microsoft不再为MSE付出任何努力。无论如何，这从来都不是一个受支持的项目。值得庆幸的是，决定不在生产运行时环境中使用MSE。

I was recently on a project where using MSE was investigated. The investigation took place in Q1 of 2011. After speaking with Microsoft representatives and a former member of the MSE team, we found that Microsoft is no longer putting any effort into MSE. It was never a supported project anyways. Thankfully the decision was made not to use MSE in the production runtime environment.

在该项目之前，我与另一个客户在一个不同的项目中，使用MSE的时间很短。简要说明原因。从UI的角度（对于任何大量服务几乎是不可用的）和从限制的角度来看，我们都发现MSE很难使用。 MSE确实具有一些非常酷的功能，例如使您能够虚拟化端点，但是IMO不值得。

Prior to that project I was on a different project with a different client where MSE was used for a brief period of time. Brief for a reason. We found MSE very difficult to use, both from a UI standpoint, which is pretty much unusable for any large number of services, and from a limitations standpoint. MSE does have some very cool features, like giving you the ability to virtualize endpoints, but it's not worth it IMO.

由于它充当经纪人，因此成为瓶颈和单点故障。没有一种好方法可以在环境之间迁移配置（一开始是很麻烦的），如果您搞砸了一个配置，最终可能会恢复数据库。另外，由于MSE充当经纪人，您将失去交易的WCF功能（这是一个大问题）。

Since it acts as the broker, it becomes a bottleneck and a single point of failure. There isn't any good way to migrate configurations (which are hell to begin with) from environment to environment, and if you screw one up, you could end up restoring your database. Also, since MSE is acting as the broker, you lose the WCF capability of transactions (which is a big problem).

此外， MSE网站指出，MSE已到使用寿命，并提出了替代方案。它还指出，将不再发布任何版本，并阻止其在生产中使用：

Additionally, the MSE website states that MSE has reached end of life and suggests alternatives. It also states that there will be no further releases and discourages its use in production:

2009年12月的CTP版本是MSE的最终版本。 ）最后，我们想引导您转到许可协议中有关支持条款的第3.（E）节。作为CTP版本，我们建议您不要将其用于生产或提供支持。

"The December 2009 CTP Release was the final release of the MSE. (...) In closing, we want to direct you to section 3.(E) of the License Agreement regarding the support clause. As a CTP release we do not recommend this be used in production or provide support."

所有人都说，尽管它为您提供了一些很酷的功能，但我建议您不要使用它。您正在寻找什么治理功能？

All said, though it gives you some cool features, I would suggest that you do not use it. What governance capabilities are you looking for?

这篇关于托管服务引擎（MSE）路线图的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！