|
POJO is making a revival, because all the complexity is
being transferred from user code to deployment environment. I am optimistic that
the developments around WS-* (particularly WS-Policy, WS-MetadataExchange,
WS-Trust, WS-Security, WS-Addressing, UDDI, WSDM) will eventually enable that
sort of transformation to occur in distributed computing. As infrastructure will
be getting smarter, distributed application development should be getting
simpler.
Daniel
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of JP Morgenthal Sent: Tuesday, May 24, 2005 6:46 PM To: [email protected] Subject: RE: [service-orientated-architecture] Business case for SOA Steve,
I, like you, am not an SOA-biggot in that I’m fine if engineers want to use Web
Services as a design methodology for their application, however, it is my belief
that what that companies are doing is not proving SOA, you’re proving Web
Services. SOA would require that you design re-usable business services
that have well-defined management and security models and that defines the
policy for usage. That’s not to say that this doesn’t have value, but
realize that SOA is an infrastructure movement that defines the framework that
services are deployed and managed within. Otherwise, it’s a
component-based systems-engineering model, or just plain-old Distributed
Computing (which, BTW, I’m leaning heavily toward based on WS interfaces).
After all POJO is really making a revival, can’t
PODC? JP
From:
[email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Steve Schaffer I work with Insurance companies, and
they are proving the value of SOA | ||||||||||||||||||
smime.p7s
Description: S/MIME cryptographic signature
