ZeroMQ

Using 0mq from Ruby.

Transcript

1. http://zero.mq/ 1
2. A ØMQ socket is what you get when you take a normal TCP socket, inject it with a mix of radioactive isotopes stolen from a secret Soviet atomic research project, bombard it with 1950-era cosmic rays, and put it into the hands of a drug-addled comic book author with a badly-disguised fetish for bulging muscles clad in spandex. Yes, ØMQ sockets are the world-saving superheros of the networking world. 2
4. Problem 4
5. How to easy connect any code to any code, anywhere 5
6. Existing solutions 6
7. Connect • In-process in-proc://some-point • Unix sockets ipc://some/pipe • BSD sockets tcp://0.0.0.0:1234 • Others multicast (PGM) ... 7
8. BSD Sockets 8
9. BSD TCP * Images by Tenouk Protocols 9
10. BSD TCP UDP * Images by Tenouk Protocols 10
11. •New/Exit - socket() , close() •Configure - setsockopt() •Connect - bind() , connect() •Use - send() , recv() Sockets BSD 11
12. Problems BSD •Need to choice of transport •Stream (TCP) , datagram (UDP) •Peer-2-Peer connections 12
14. zguide.zero.mq 14
15. A ØMQ socket is what you get when you take a normal TCP socket, inject it with a mix of radioactive isotopes stolen from a secret Soviet atomic research project, bombard it with 1950-era cosmic rays, and put it into the hands of a drug-addled comic book author with a badly-disguised fetish for bulging muscles clad in spandex. Yes, ØMQ sockets are the world-saving superheros of the networking world. 15
16. in a Hundred Words ØMQ (ZeroMQ, 0MQ, zmq) looks like an embeddable networking library but acts like a concurrency framework. It gives you sockets that carry whole messages across various transports like in-process, inter-process, TCP, and multicast. You can connect sockets N-to-N with patterns like fanout, pub-sub, task distribution, and request-reply. It's fast enough to be the fabric for clustered products. Its asynchronous I/O model gives you scalable multicore applications, built as asynchronous message-processing tasks. It has a score of language APIs and runs on most operating systems. ØMQ is from iMatix and is LGPL open source. 16
17. Many languages * Images by iMatrix 17
18. Sockets •Well known API •Messages oriented •Transport agnostic •Socket-level topology 18
19. Well known API 19
20. Sockets •New/Exit - socket() •Configure - setsockopt() •Connect - bind() •Use - send() , recv() BSD 20
21. Sockets •New/Exit - zmq_socket() •Configure - zmq_setsockopt() •Connect - zmq_bind() •Use - zmq_send() , zmq_recv() 21
23. Hello world (server) 23
24. Hello world (client) 24
25. Message oriented 25
26. Message oriented Receive Send 26
27. Various transports 27
28. Various transports •req.bind(‘inproc://some/pipe’) •req.bind(‘ipc://some/pipe’) •req.bind(’tcp://127.0.0.1:5555’) 28
29. Patterns Socket level topology 29
30. Request - Reply * Images by iMatrix 30
31. Publish - Subscribe * Images by iMatrix 31
32. Parallel tasks * Images by iMatrix 32
33. Demo 33
34. Scale 34
35. Start small * Images by iMatrix 35
36. Bigger * Images by iMatrix 36
37. And bigger... * Images by iMatrix 37
38. Devices * Images by iMatrix Device 38
39. QUEUE * Images by iMatrix 39
40. Demo 40
41. Implementation 41
42. Ruby-FFI Foreign Function Interface 42
43. Ruby-FFI 43
44. Ruby-FFI (Win) 44
45. Why FFI? •Debian: no need from *-dev •Multi-platform •Easy to read (Ruby, not C) 45
46. Projects http://zeromq.org/docs:labs 46
47. http://mongrel2.org 47
49. Evolution HTTP Net App HTTP Net App HTTP Net App Webrick Mongrel Thin 49
50. Evolution HTTP Net App Mongrel2 50
51. Mongrel2 0mq Handler Handler Handler Responses Requests Push/Pull Pub/Sub 51
52. Demo 52
53. Future •Part of Linux kernel •http://www.crossroads.io/ •zerocloud ? 53
54. Thank you! 54
55. Sockets •New/Exit - socket() •Configure - setsockopt() •Connect - bind() •Use - send() , recv() BSD 55
56. Sockets •New/Exit - zmq_socket() •Configure - zmq_setsockopt() •Connect - zmq_bind() •Use - zmq_send() , zmq_recv() 56
58. Hello world (server) 58
59. Hello world (client) 59