The SOA configures the data about the domain to define which servers are classed as authoritative (that is, then give qualified responses to queries for this domain).
From now on, any service that accesses Google's Contacts API - which makes it easy to import your list of friends' and coworkers' email addresses into another service - will need to offer reciprocity.
This guarantees that that the client always accesses up-to-date service binaries, which is especially important for debugging scenarios such as stepping from client code into service code.
An example of this is when a service provider accesses multiple back-end systems with different timeout requirements, but only determines at run time which back-end is invoked.
Matching work partitions to their data partitions will increase the probability of a cache hit within the server and decrease remote accesses to the database, which introduces quite a bit of latency.
Third, I wanted to provide a working prototype that illustrates many of the critical needs for a transaction coordination service, such as how to manage stateless service calls.
Then developers tie it together on the back end and the service consumers have something to write against on the front end and it all kind of meets in the middle.