William Henry wrote:
> I think that it would be helpful to create some sort of maturity
> matrix that allows companies to self assess what various aspects
> "SOA" they require in the short term and also in the long term (Think
> Big, Start Small, Scale Fast). It would benefit the industry more if
> this was part of the standards instead of vendor controlled. It would
> not only speed up adoption but would also help guarantee more
> successful deployments.
This is the most predominant reason why I absolutely refuse to jump on the
webservices bandwagon. With Jini/Java, I am in control of my architecture. I
can start out small, and grow the architecture to support the features I need.
My ongoing mantra about mobile code is all about this issue of scaling service
implementations independent of the programatic interfaces. The fact that the
webservices crowd is favoring big business opportunities create a lot of the
"there are no small solutions" statements. The lack of programatic interfaces
into some of these systems also means that I can't add features that I need.
Instead, I'd have to wait for the vendor to provide a particular feature that
integrates with their system.
Gregg Wonderly
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
