Cart
[Home] [By Thread] [By Date] [Recent Entries]
> -----Original Message----- > From: Rich Salz [mailto:rsalz@d...] > Sent: Monday, November 29, 2004 7:23 PM > To: Dare Obasanjo > Cc: Mark Baker; Chiusano Joseph; xml-dev@l... > Subject: RE: Web Services/SOA (was RE: > XML 2004 weblog items?) > > > Or is there an 'RPC architectural style' that I am unaware of? > > Yes: a "method name" and calling sequence (e.g., multiple > parameters) and return value. In SOA, you think more of > sending XML documents around and there's only one method, > probably POST, and some meta-data, like a URI/URL. > > It is admittedly kinda fuzzy-wuzzy, but that's not uncommon > when you start talking about "architecture." :) So SOA is RPC with a calling convention for methods? Sounds silly to me. I like Don's four fundamentals of service orientation from http://msdn.microsoft.com/msdnmag/issues/04/01/Indigo/default.aspx * Boundaries are explicit * Services are autonomous * Services share schema and contract, not class * Service compatibility is determined based on policy It's basically a philosophy on how one should treat building distributed application instead of a way to repackage yesterday's technology with today's buzzwords so one can charge an arm and a leg for building applications with tomorrow's toolkits. I especially like the fact that it's quite easy to see how RESTful applications are service oriented using those guiding principles. -- PITHY WORDS OF WISDOM Ade's Law: Anybody can win -- unless there happens to be a second entry. This posting is provided "AS IS" with no warranties, and confers no rights.
|
