On 05/07/06, Mark Baker <[EMAIL PROTECTED]> wrote: > > > > > > > > > On 7/5/06, Steve Jones <[EMAIL PROTECTED]> wrote: > > Which was the bit I'm trying to get across in saying that SOAP v REST > > is a pointless debate. The consumer of the service cares only about > > what happens, not about the mechanism to achieve it. I'm not arguing > > that REST is wrong and should never be used, just that its not > > actually important enough to argue over the bit in between. > > > It's important because the choice of architectural style effects > scalability, reliability, simplicity, etc, and those things are > important to customers. > > If your customer wanted you to build a large system for them, suitable > for integrating disparate systems together, both their own and those > of their partners & customers, would you start with a scalable > architectural style, or a non-scalable one? The choice is as simple > as that, I'm afraid.
I'd start with determining what the services are that are going to be shared, their drivers, principles and the capabilities that they provide access to. Next up I'd look at the business case for each of the services and the system as a whole and determine what value they aimed to deliver and the type of service lifecycle each one would have. I'd then worry about formalising the definition of those services and agreeing with people how the services are to be consumed. I'd worry next about the NFRs of the services and their interaction patterns, then I'd worry about the skills of the developers available to build the system. Then I'd worry about how the system would need to be supported and changed and what was currently available or needed to be made available to make that successful. Then I'd sit down and think about the best way given these constraints to build the system that would enable it to scale to a level that meets its NFRs with a reasonable contingency. Unless you are saying that REST = scalable and SOAP = non-scalable? Which is (IMO) a tad brave as a statement. ------------------------ Yahoo! Groups Sponsor --------------------~--> See what's inside the new Yahoo! Groups email. http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
