I read an article on the DevX web site entitled “Virtualize Your SOA with the Managed Services Engine” by Steve Spefanovich. I had not heard about the Managed Services Engine (MSE) before. So I read through it with interest.
Steve said that it is difficult to keep the enterprise SOA up and running. The MSE is a product that eases this pain. Steve reviewed the Windows Communication Foundation (WCF). He said that WCF is split between contract and implementation.
The MSE uses the idea of service virtualization. It provides a service layer on top of the services you provide. The MSE extends rather than replaces the WCF. It acts as a proxy service host, which is the only point of entry to your SOA.
The four major parts to the MSE are the service catalog, messenger, broker, and dispatcher. The MSE runtime server can act as a messenger, as a broker, or both a messenger and broker. It can import existing services. It is also able to version the services you provide.
Only the published service is listed in the WSDL. You can only publish one version of your service at a time. The MSE eliminates tight coupling between consumer and service.
Use the Requirements Already - I am working on a release at work. Initially we were supposed to replicate some bunch of database tables that the customer had in an old system. We did a ...