SOAP and/or REST and/or WebSocket

This BOF is a lively discussion comparing SOAP, REST, and WebSocket architectures, asking questions such as
• When to use which?
• Should SOAP and/or REST be used in a complementary way where request/response are handled with SOAP and/or REST/XHR and push/pubsub/broadcast are provided by WebSocket?
• Can REST and WebSocket coexist, given that REST is stateless (scalability via caching) whereas WebSocket connections are stateful (scalability via load-balancing)?
• Are WebSocket apps creating siloed applications instead of REST-like, addressable resources?
• If you do REST over WebSocket, how do you represent HTTP methods, URIs, URI parameters, and headers?
Be sure to attend and bring your opinion. This should be fun.

Copyright © 2013 Oracle and/or its affiliates. Oracle® is a registered trademark of Oracle and/or its affiliates. All rights reserved. Oracle disclaims any warranties or representations as to the accuracy or completeness of this recording, demonstration, and/or written materials (the “Materials”). The Materials are provided “as is” without any warranty of any kind, either express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, and non-infringement.