|
+1 on the comment that web services are not objects. Just because we can deploy a class as a web service, doesnt mean that this is good design.
Yes, we get the ability to compose an application past compile time, but why o why would I want to build up an application this way...inheritance hierarchies and OO classes should stay in the application, albeit there are sometimes when this is useful esp in integration scenarios, where the unit of functionality can be much finer grained.
a good mantra too chant is that web services should expose 'coarse grained business services'...then application composition is a more an exercise in satisfying human requirements, rather then application/system level requirements.
without sounding too strident, OO has been touted as *the* approach for all software development, its my feeling that a particular approach is good to get you to a certain level; I suspect that leaps in hardware performance will start coming into play with respect to auto generation of code, esp the applicaiton composition opportunities that SOA brings to software development. The re-emergence of functional programming (XSLT ) and hierarchical data models ( XML ) in mainstream programming, should be proof enough that we are better off with a hybrid approach, instead of being hypnotised by any one method.
cheers, jim fuller
|
Previous Message
