Today almost every project involves some sort of distribution: interaction with some legacy system, some sort of authentication service, etc. Teams tend to solve the distribution problem by applying easily understandable RPC-style technologies. Not that RPC-style communication broken by definition, but it tends to make some very strong assumptions on the channel and the availability of the remote component.
The implicit assumptions
From developer perspective RPC looks very attractively: the remote object looks just like it it was on the same machine - the undelying technology takes the responsibility for serializing requests and deserializing method returns back. Just like calling a local...
posted @ Sunday, July 12, 2009 7:47 PM |