This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: Common SOA pitfalls
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
"My organization has a major initiative to move to SOA and we're in the process of laying down some standards for how services will be classified, built, etc.
Following some general guidance from MSFT and others we've created the following service taxonomy.
Process Services - represents a long running business process
Activity Services - represents atomic operations that encapsulate interaction with more than one entity service
Entity Services - represents interaction with a single business entity (e.g. customer)
Common Services - represents common functionality available for use by other services such as address validation, credit card authorization etc."
DO NOT DO THIS.
You should only have one kind of service, and that is a business service. Accounting is a good example. All those other technical mumbo-jumbo things are internal to a service.
If you want re-use across services, use components.
Wrapping a component (like address validation) with WSDL does not a service make.