March 2006
REST wins, no-one goes home [@lesscode.org]
(via)Let’s be realistic. No software architecture can truly withstand implementation. REST is really great, but on the web, there is plenty of detail work to be cleared out, like push, containership, encoding, side-effected GETs, curse-of-popularity, queuing, 2 versus 4 methods, universal format junk, and authentication, among others. I could go on, it’s messy out there.
March 2005
Evaluating SOAP for High Performance Business Applications: Real-Time Trading Systems
(via)Web services, with an emphasis on open standards and flexibility, may provide benefits over existing capital markets integration practices. However, web services must first meet certain technical requirements including performance, security and fault-tolerance. This paper presents an experimental evaluation of SOAP performance using realistic business application message content.
Making the Right Choices for SOAP Scalability
(via)Each choice that you make affects the scalability and reliability of your finished application, especially when you build Web services. For example, as you will learn in this article, my study of SOAP encoding styles found a 30-fold performance improvement by choosing one SOAP encoding-style over the others. By understanding the performance impact of SOAP encoding styles, Web service development tools, application servers, and platforms, our choices greatly improve system performance.
1
(3 marks)
