This link has been bookmarked by 41 people . It was first bookmarked on 13 Aug 2007, by Fyun Li.
-
03 Nov 14
-
31 Mar 14
-
Everything needed by the service to provide its functionality should be passed to it when it is invoked.
-
A service invocation is not a remote procedure call.
-
Following the principle of loose coupling, a service provider can not rely on the consumer’s ability to reuse any code that it provides in its own environment; after all, it might be using a different development or runtime environment.
-
the functionality, syntax and semantics of the provider must fit the consumer’s requirements,
-
the technical capabilities and needs must match.
-
Services can be changed and deployed, versioned and managed independently of each other. A service provider can not rely on the ability of its consumers to quickly adapt to a new version of the service; some of them might not even be able, or willing, to adapt to a new version of a service interface at all (especially if they are outside the service provider’s sphere of control).
-
To ensure the utmost accessibility (and therefore, long-term usability), a service must be accessible from any platform that supports the exchange of messages adhering to the service interface as long as the interaction conforms to the policy defined for the service.
-
To interact with services, data is passed as documents. A document is an explicitly modeled, hierarchical container for data. Self-descriptiveness is one important aspect of document-orientation. Ideally, a document will be modeled after real-world documents, such as purchase orders, invoices, or account statements. Documents should be designed so that they are useful on the context of a problem domain, which may suggest their use with one or more services.
-
Most SOA proponents will agree that loose coupling is an important concept. Unfortunately, there are many different opinions about the characteristics that make a system “loosely coupled”.
-
A key principle to be followed in an SOA approach is the reliance on standards instead of proprietary APIs and formats.
-
The most important aspect of any standard is its acceptance (which basically translates to "Microsoft needs to be on the author list" in case of Web services).
-
As a result, a service provider or service consumer can be built using any technology that supports the appropriate standards, not restricted by any vendor roadmap.
-
All of the metadata artifacts within the overall SOA need to be stored in a way that enables them to be discovered, retrieved and interpreted at both design and run time.
-
-
19 Aug 13
-
03 Sep 11
-
23 Nov 10
-
26 Oct 10
-
20 Oct 10
-
26 Apr 10
-
20 Apr 10
-
07 May 09
-
23 May 08
-
11 Mar 08
-
14 Nov 07
-
15 Oct 07
Pawel RogowiczIn this article, InfoQ's Stefan Tilkov, consultant at innoQ, proposes 10 principles to serve as a basis for SOA discussions. The list starts with Don Box's four tenets (service with explicit boundaries, shared contract and schema, policy-driven, and au...
-
05 Oct 07
-
10 Sep 07
-
13 Aug 07
-
29 May 07
-
19 May 07
-
17 May 07
-
07 May 07
-
29 Mar 07
-
10 Mar 07
-
06 Mar 07
-
01 Mar 07
-
28 Feb 07
-
27 Feb 07
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.