The Artima Developer Community
Sponsored Link

.NET Buzz Forum
Common SOA pitfalls

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Udi Dahan

Posts: 882
Nickname: udidahan
Registered: Nov, 2003

Udi Dahan is The Software Simplist
Common SOA pitfalls Posted: Feb 26, 2006 1:27 PM
Reply to this message Reply

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.
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Udi Dahan
Latest Posts From Udi Dahan - The Software Simplist

Advertisement
I just saw this today:

"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.

Read: Common SOA pitfalls

Topic: [Tool] Windows Defender for German-speaking Audience Previous Topic   Next Topic Topic: How to Get your Projects Noticed by Microsoft

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use