Websocket Messaging Patterns

Transcript

1. Messaging Patterns + WebSockets
2. Me • I write full stack javascript • I work at Fractal • I like to code • I love open source
3. SOAP
4. Just kidding
5. Websocket? • Bidirectional • Always open • Less overhead than HTTP • Faster • Binary data • “Real-time web cloudscale 3.0”
6. Browser Support Use shims
7. Implementations • Socket.io • Engine.io • SockJS • ws
8. RPC • Remote Procedure Call • Request-Response cycle
9. Server Client Request Response Thinking…
10. RPC History • Used to be a big deal for cross-process communication • REST/HTTP knocked it out of the game • WebSockets are bringing it back
11. RPC – Use Cases • Scaling procedures horizontally • Replacement for REST over HTTP • Communicating between the client and server
12. RPC – Example Sequence • Client sends request for procedure “hello” with arguments [“world”] • Server receives and unpacks message • Server calls procedure “hello” with arguments [“world”] • Server sends response with procedure return value • Client handles response
13. RPC - Implementations • Vein • DNode • NowJS* • jsonrpc2
14. PubSub • Client (subscriber) subscribes to a topic • Client (publisher) publishes a message about the topic without knowledge of subscribers • Similar to EventEmitter
15. PubSub - Diagram
16. PubSub – Use Cases • Chat • Watching realtime changes – Whiteboards – File collaboration – Auction/trading systems
17. PubSub – Example Sequence • Subscribers (Client A and B) subscribe to channel “test” • Publisher (Client C) publishes message “hey” to channel “test” • Client A and B receive message “hey” on channel “test”
18. PubSub - Implementations • Pulsar • Socket.io • PubNub (PubSub as a service)
19. DSTM • Distributed Software Transactional Memory • Shared object between all clients • Changes to the shared object happen in “transactions” • Changes to the shared object are synchronized between all clients • Conflict resolution guarantees atomic transactions
20. DSTM - Diagram Server Object Conflict Resolution Object Conflict Resolution Clients Clients
21. DSTM – Use Cases • Data synchronization • Distributed/scalable systems • Financial transactions • Anything where accuracy is involved
22. DSTM – Example Sequence • Client A connects and receives object • Client B connects and receives object • Client B changes key “hello” to “world” • Client A changes key “hello” to “code camp” • Transaction from Client A is rejected due to conflict – synchronization is forced • Client A retries it’s transaction
23. DSTM – Implementations • Warlock • AtomizeJS
24. “Fat Client” - The Philosophy • Lower server requirements • Working offline • Higher server capacity • Scales easily • Uses less bandwidth
25. “Fat Client” – Example Sequence • Client A receives index.html which then loads all static resources • If Client A needs something from the server it is either work or message passing which can be done over WebSockets • After the initial grab of static files everything is done via WebSockets
26. Questions?
27. Sandbox
28. End • Follow me on Twitter @eschoff @wearefractal