I am interested in this particular conversation as well, so am looking forward to the responses.
Performance is very important but I don't think folks have a common definition of what performance is. In addition, in a majority of the cases, performance is not treated as something that should be engineered into a solution from the ground up. One of the first things that I do when folks start this particular conversation is to point them them to some work that has been done by J.D. Meier and his team over at Microsoft as part of their Perf & Scale work. In particular I point them over to the following: Fundamentals of Engineering for Performance http://msdn2.microsoft.com/en-us/library/ms998534.aspx Performance Modeling http://msdn2.microsoft.com/en-us/library/ms998537.aspx Design Guidelines for Application Performance http://msdn2.microsoft.com/en-us/library/ms998541.aspx I find the above work relevent, and highly recommended reading, whether or not you are in the .NET/Microsoft camp. Regards, - Anil -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Jones Sent: Friday, October 27, 2006 7:00 PM To: [email protected] Subject: [service-orientated-architecture] Performance... how important is it? While I bang on about technology not being important with SOA, I'd like to kick a thread off around one of my perceptions. Anne said at the SOA event in Belgium this week that she'd recommend XML gateways for performance reasons. My view (and the experience I've had tends to back this up) is that XML performance is rarely an issue. The cost of marshaling WS against RMI is minimal in most cases, and when using a StAX parser for fragments of a large document then the WS approach will be much quicker than RMI. And generally with the current hardware performance characteristics (My laptop is a 2-way 2GHz box) the challenge isn't on the computational side for performance around XML processing but still in elements like databases, transaction managers and of course the actual IO (like disk) and bandwidth elements. Note here I'm talking about the 95%+ of applications which measure end-to-end performance in the second or 1/10 second margins, not at the micro-second level. So while XML might be one of the most inefficient transports ever dreamed of. Is it really an area where most organisations should worry about performance given the current hardware characteristics? What is the experience out there? Is XML performance really that bad in most software stacks that dedicated solutions are required? Stats and data most appreciated. Steve Yahoo! Groups Links Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/service-orientated-architecture/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> 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/
