A Guide to Implementing Service Oriented Event Management, Part 1

My previous post discussed some of the problem domain I am facing with implementing autonomous services that need to communicate with one another in an asynchronous fashion without necessarily implementing something like a BizTalk.

I need something fairly light weight that is quick and easy to build, has minimal moving parts so that it is easy for another developer to pick up and extend and/or maintain as well as be easy to debug and control.

I have decided to also take advantage of the recently released Web Service Software Factory to follow best practices in structuring my project as outlined in a recent Architecture Journal article. Out of the box, I have a project structure that is built, linked and ready to go, with corresponding guidance for how it all links together.

I have partitioned out web services in the past using some of these techniques but never to this degree. I really like the concept behind this and am anxious to see how the development experience is in using this guidance automation.

To get started, I’ll define my data model and then generate my Business Entities. Yes, I said generate. It can’t be reflected in the screen shot, but each of these projects has special context menu items when you right click on the project file in Visual Studio that gives you options as part of the guidance to generate different parts of the solution all the up the entire stack.

More to come in subsequent postings.