SOA Guerrilla (Jim Webber) , ESB and SOA

Jim Webber explains here http://jim.webber.name/2007/10/17/2ae26134-ea19-43de-9a75-d5ef62c0e5b4.aspx
the dangers on why you should not burry your integration, transformation etc in the ESB. (Well why you should not use a proprietary ESB). I myself I am not against it of having an ESB but you should follow standards to stop vendor lock in (BPEL) for system to system processes, and just use the ESB to simplify the management of your SLA (QoS), temporary contract resolution and management of policies, and even addressing. (its just a tool!)

Using standards on web services like WCF and WSIT you can achieve things like policy, reliable messaging, transaction support etc, but nevertheless the ESB will help you on said maintainability.

The majors risk is that the ESB sometimes won’t manage to comply as quick with new standards as development tools (You can overcome this by temporarily bypassing the bus until these are available)… and don’t forget that you will need good governance to don’t replicate or create new spaghetti.

And remember the 4 tenets of SOA: http://www.bpminstitute.org/articles/article/article/the-four-tenets-of-service-orientation.html

Continuous Production - Production-ready software…any time

I have found this article on Test Early » Continuous Production - Production-ready software…any time.

And I defenetly agree with the article but in an enterprise enviroment also a good architecture based around Decoupling: SOA, BPM, Composite Applications (portlets, cap, wcsf), Modularitation, dependency injection, and Governance around depencies: services, object, modules will allow you to succeed!!

Enable the Create Translator recipe for all projects.

Well I am back using the Software Factories, and currently using the the Web Client Software Factory June 2007 and the Web Service Software Factory Modelling Edition 2008 CTP both in Visual Studio 2008 Team System. They are defenetly the best way to enforce, teach good patterns to your teams to deliver a good set of maintanable code.

Our agile approach meant that we needed to have installed both factories side by side on the same machine and to overcome the issue that the GAX / GAT is only able to run in either 2005 or 2008 (Orcas) I decided to run WCSF in 2008 following the instructions of Ezequiel.

The Web Client Software Factory does not have the Create Translator recipe so whilst I could translate my model to my data contracts in the WSSF i could not translate my Datacontracts to my client model. After a bit of playing around I have managed to enable it, so here are the steps:
1. Have installed the Web Service Software Factory. :)

2. Modify the file:
%Program Files%\Microsoft Service Factory V3\Guidance Package\Recipes\Binding.xml

From:

<action referencetype="Microsoft.Practices.ServiceFactory.References.ProjectIsInRoleReference, Microsoft.Practices.ServiceFactory.GuidancePackage" role="ServiceRole" type="RefCreator" assetname="CreateTranslator" name="CreateTranslatorRef">

To:
<action referencetype="AnyStandardProjectReference" type="RefCreator" assetname="CreateTranslator" name="CreateTranslatorRef">

3. Close all instances of Visual Studio.
4. Open Visual Studio , go to Guidance Packages and add the Web Service Software Factory.
Note: If it is already there remove it and added it again to refresh the bindings
5. In the project you are creating add a folder “GeneratedCode".