Good service, happy customer....

Nope, I'm not gonna talk about SOA in this post. I only mention few things about service concept.

Let say somehow (whatever you selected to implement a service, might be CORBA or Web Services) you gonna implement a service. The first thing you should consider is the Quality of the Service. Without any sign of quality of your service (sign of quality??? that's another story) that your application would be built upon it, it's not possible to make your application's customers happy.

Furthermore, another thing you should consider when building a web service is easiness of maintenance and management.

My point is,

1. If you consider to create a service, think on dependencies. Because stability is the main point of services. If your service is not stable, then what is it good for?
2. Do not try to, or force to, use Web Services just for show off and say that "we're using SOA, aren't you?" geek. Is Web Service the right enabler? Consider more reliable and mature distributed computing technologies like RMI, CORBA etc. Because SOA isn't Web Services or vice versa.