Is not everyone more or less in "violent agreement"
here? I don't think anyone is trying to force any particular standard or
technology on anyone else, just trying to get the best out of things to speed
development and service availability along.
However, I'd still like to see a couple of usage
scenarios using Java/Jini to build composite applications consisting of both new
and 3GL code. I suspect these can and will be built using a variety of
technologies, including Web Services.
Personally, I think we should be looking at these
things from a more practical level, size not being relevant, technologies not
that relevant either, service and ease of development and maintenance being the
important parts.
No point having the best set of technologies in the
world if 1) they take years to understand, 2) are in some way proprietary and 3)
do not allow the integration of existing code.
Regards, john
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Gregg Wonderly
Sent: Wednesday, February 08, 2006 21:35
To: [email protected]
Subject: Re: [service-orientated-architecture] Governance patterns?
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
SPONSORED LINKS
| Service-oriented architecture | Computer monitoring software | Computer and internet software |
| Free computer monitoring software |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
