But you can't ignore the data issue. The data is the essence of the application semantics.

Anne

On 7/6/06, Mark Baker < [EMAIL PROTECTED]> wrote:

On 7/6/06, Steve Jones <[EMAIL PROTECTED]> wrote:
> Now either I've been incredibly lucky or I only build mickey mouse
> apps... but I've never had this problem.

Another possibility is that you don't realize how simple things can
really be? That's how it was for me, at least.


> What form of scalability are you refering to?

Number of services. With Web services, for each new service that's
added to the system, in order for existing components to be able to
communicate with it, you have to modify them (ignoring the data issue,
which is the same with both). Not so with REST.

In technical terms, integration complexity with Web services is
typically O(NlogN) (O(N^2) worst case). With REST it's O(logN) (O(N)
worst case). There are even REST extensions where you can achieve
O(1) at scale (e.g. weblog aggregation, search). SOA is totally
heading in the wrong direction in terms of scaling.

Mark.


__._,_.___


SPONSORED LINKS
Computer software Computer aided design software Computer job
Soa Service-oriented architecture


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to