WAMP as a platform for composite SOA applications and its implementation on Lua
•
0 gefällt mir•811 views
WAMP stands for Web Application Messaging Protocol. This is an open protocol that implements two patterns within a single protocol: RPC and Publish / Subscribe. As it seems to me, this is a great platform for the Internet of Things, Smart City and in general business applications with a lot of different components and services.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Ähnlich wie WAMP as a platform for composite SOA applications and its implementation on Lua
Ähnlich wie WAMP as a platform for composite SOA applications and its implementation on Lua (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
WAMP as a platform for composite SOA applications and its implementation on Lua
- 1. WAMP as a platform for composite SOA applications and its implementation on Lua Konstantin Burkalev @KSDaemon
- 2. Few words about me… 2 • Software architect • 15+ years in IT • Author and host of podcasts: SDCast & RadioJS • Active member of WAMP protocol development group • Author and maintainer of a few WAMP implementations, some of them are written in Lua
- 35. The system informs about found devices Bath room Living room Task: Smart Home System 4 User Admin
- 36. The system informs about found devices Bath room Living room Task: Smart Home System 4 User Admin
- 38. What is WAMP 5
- 41. What is WAMP • It stands for "Web Application Messaging Protocol" • Is intended for communication between software components in near real-time • Provides two mechanisms: • Publish/Subscribe (PubSub) • Remote Procedure Calls (RPC) 5
- 42. What is WAMP • It stands for "Web Application Messaging Protocol" • Is intended for communication between software components in near real-time • Provides two mechanisms: • Publish/Subscribe (PubSub) • Remote Procedure Calls (RPC) • Bi-directional, ordered 5
- 43. What is WAMP • It stands for "Web Application Messaging Protocol" • Is intended for communication between software components in near real-time • Provides two mechanisms: • Publish/Subscribe (PubSub) • Remote Procedure Calls (RPC) • Bi-directional, ordered • For communication between clients is required WAMP-router 5
- 44. Why WAMP? 6
- 47. Why WAMP? • Open specification • Thoughtful Publish / Subscribe • Thoughtful Remote Procedure Calls 6
- 48. Why WAMP? • Open specification • Thoughtful Publish / Subscribe • Thoughtful Remote Procedure Calls • Message routing 6
- 49. Why WAMP? • Open specification • Thoughtful Publish / Subscribe • Thoughtful Remote Procedure Calls • Message routing • Cross-platform 6
- 50. Why WAMP? • Open specification • Thoughtful Publish / Subscribe • Thoughtful Remote Procedure Calls • Message routing • Cross-platform • There are implementations in more than 15 languages 6
- 51. WAMP alternatives 7 Technology PubSub RPC Routed RPC Web native Cross Language Open Standard WAMP ✔ ✔ ✔ ✔ ✔ ✔ AJAX - ✔ - ✔ ✔ - AMQP ✔ (✔) - - ✔ ✔ Java JMS ✔ - - - - ✔ JSON-RPC - ✔ - ✔ ✔ ✔ MQTT ✔ - - - ✔ ✔ REST - ✔ - ✔ ✔ - SOAP - ✔ - ✔ ✔ ✔ socket.io ✔ - - ✔ - - XMPP ✔ - - ✔ ✔ ✔ ZMQ ✔ - - - ✔ -
- 61. WAMP architecture 17 Serializer. All messages are serialized using JSON/MessagePack/ CBOR. message
- 64. Basic WAMP concepts • Client. Can provide or consume resources, such as subscriptions and RPC. • Router. Deals with authorization and message routing between clients. • Peer. Can be a client or a router, must have at least one role. • Role. Determines the capabilities of the node. There are 4 client roles and 2 router roles. • Session. It is necessary to identify and authorize clients, announce the role of nodes. • Realm. Domain, namespace, within which messages are routed. • Transport. You can use: WebSockets, Raw TCP, Unix sockets and even HTTP Long poll. • Serializer. Messages are serialized using JSON / MessagePack / CBOR / etc. • Resource identifiers, URIs. Required for topics, procedures and errors. 19
- 68. WAMP: Features • Basic profile: basic features of RPC and PubSub • Advanced profile: • Challenge-Response Authentication • Progressive call results, call timeout, call canceling • Publication / call trust levels • Caller / publisher identification • Pattern based registration / subscription • Shared registration, sharded registration / subscription • Event history • Meta API & Procedure / topic reflection 20
- 73. WAMP: session establishment 21 HELLO WELCOME GOODBYE (init by client) ABORT Client Router Realm [6, {"message": "The host is shutting down now."}, "wamp.error.system_shutdown"]
- 74. WAMP: session establishment 21 HELLO WELCOME GOODBYE (init by client) ABORT GOODBYE Client Router Realm [6, {}, "wamp.error.goodbye_and_out"]
- 75. WAMP: session establishment 21 HELLO WELCOME GOODBYE (init by client) ABORT GOODBYE GOODBYE (init by router) Client Router Realm [6, {}, "wamp.error.close_realm"]
- 76. WAMP: session establishment 21 HELLO WELCOME GOODBYE (init by client) ABORT GOODBYE GOODBYE GOODBYE (init by router) Client Router Realm [6, {}, "wamp.error.goodbye_and_out"]
- 77. WAMP: session establishment 21 HELLO WELCOME GOODBYE (init by client) ABORT GOODBYE GOODBYE GOODBYE (init by router) Client Router Realm
- 123. WAMP: real projects • Kadecot API Server. Sony Computer Science Laboratories • ParaView. Parallel Data Analysis and Visualization Application, Kitware • Record.Evolution. Data-warehouse and Business Intelligence 28
- 124. WAMP: real projects • Kadecot API Server. Sony Computer Science Laboratories • ParaView. Parallel Data Analysis and Visualization Application, Kitware • Record.Evolution. Data-warehouse and Business Intelligence • SmartME smart city project. MDS Lab at the University of Messina 28
- 125. WAMP: real projects • Kadecot API Server. Sony Computer Science Laboratories • ParaView. Parallel Data Analysis and Visualization Application, Kitware • Record.Evolution. Data-warehouse and Business Intelligence • SmartME smart city project. MDS Lab at the University of Messina • ButterflyDNS. Web UI frontend for BIND DLZ • Gollard VISION Server Management Subsystem 28
- 130. Loowy: WAMP client in Lua 30 • Works in Lua/Luajit environment on top of lua-ev • Supports JSON and Msgpack serializers • Supports a number of features from Advanced Profile
- 131. Loowy: WAMP client in Lua 30 • Works in Lua/Luajit environment on top of lua-ev • Supports JSON and Msgpack serializers • Supports a number of features from Advanced Profile • Automatic reconnection and re-subscription
- 132. Loowy: WAMP client in Lua 30 • Works in Lua/Luajit environment on top of lua-ev • Supports JSON and Msgpack serializers • Supports a number of features from Advanced Profile • Automatic reconnection and re-subscription • TODO: Raw socket transport • TODO: Meta API • TODO: Challenge-Response Authorization (WAMP-CRA) • TODO: work on the basis of coroutines
- 133. Loowy: api calls examples 31 client = loowy.new("ws://localhost/ws/", { realm = "gv" }) client:publish('sensor.events', { sensorId = 12, temperature = 27}) client:subscribe('sensor.events', function(event) -- process received event end) client:call('dcs.fan.control', true, { onSuccess = function() -- fan turned on successfully end, onError = function(err) -- error occurred end })
- 135. Loowy: Technology stack 32 • Lua 5.1+, Luajit 2.0 • lua-websockets (which uses luasocket under the hood) • lua-ev • lua-rapidjson • lua-MessagePack (optional)
- 138. Wiola: WAMP router in Lua • Works on top of Nginx/Lua module • Uses Redis for runtime storage 33
- 139. Wiola: WAMP router in Lua • Works on top of Nginx/Lua module • Uses Redis for runtime storage • Supports JSON and Msgpack serializers 33
- 140. Wiola: WAMP router in Lua • Works on top of Nginx/Lua module • Uses Redis for runtime storage • Supports JSON and Msgpack serializers • Supports a number of features from Advanced Profile 33
- 141. Wiola: WAMP router in Lua • Works on top of Nginx/Lua module • Uses Redis for runtime storage • Supports JSON and Msgpack serializers • Supports a number of features from Advanced Profile • TODO: Raw socket transport • TODO: Meta API • TODO: lua-resty-postgres 33
- 143. Wiola: Technology stack 34 • Nginx or OpenResty, simply put lua-nginx-module • lua-resty-websocket • lua-resty-redis • Redis Server • lua-rapidjson • lua-resty-hmac (optional, is required for WAMP-CRA) • lua-MessagePack (optional)
- 144. Wiola: Nginx config 35 location /ws/ { set $wiola_socket_timeout 10; set $wiola_max_payload_len 65535; lua_check_client_abort on; header_filter_by_lua_file /lib/wiola/headers.lua; content_by_lua_file /lib/wiola/handler.lua; }
- 148. Wiola: JSON caveats and limitations • cJSON • you cannot specify how to serialize empty tables 37
- 149. Wiola: JSON caveats and limitations • cJSON • you cannot specify how to serialize empty tables • lua-resty-libcjson 37
- 150. Wiola: JSON caveats and limitations • cJSON • you cannot specify how to serialize empty tables • lua-resty-libcjson • not able to work with large numbers (int > 32bit) 37
- 151. Wiola: JSON caveats and limitations • cJSON • you cannot specify how to serialize empty tables • lua-resty-libcjson • not able to work with large numbers (int > 32bit) lua-rapidjson 37
- 152. Wiola: JSON caveats and limitations • cJSON • you cannot specify how to serialize empty tables • lua-resty-libcjson • not able to work with large numbers (int > 32bit) lua-rapidjson • So far, no new problems have been found :) 37
- 156. Wiola: Runtime storage options 38 • Global variables in memory • are created every time on request handler • problems with concurrent requests
- 157. Wiola: Runtime storage options 38 • Global variables in memory • are created every time on request handler • problems with concurrent requests • Module variables loaded in init_by_lua
- 158. Wiola: Runtime storage options 38 • Global variables in memory • are created every time on request handler • problems with concurrent requests • Module variables loaded in init_by_lua • You can read in all workers
- 159. Wiola: Runtime storage options 38 • Global variables in memory • are created every time on request handler • problems with concurrent requests • Module variables loaded in init_by_lua • You can read in all workers • But the write, thanks to CoW, will create a copy of the module for the VM
- 160. Wiola: Runtime storage options 38 • Global variables in memory • are created every time on request handler • problems with concurrent requests • Module variables loaded in init_by_lua • You can read in all workers • But the write, thanks to CoW, will create a copy of the module for the VM • ngx.shared.DICT
- 161. Wiola: Runtime storage options 38 • Global variables in memory • are created every time on request handler • problems with concurrent requests • Module variables loaded in init_by_lua • You can read in all workers • But the write, thanks to CoW, will create a copy of the module for the VM • ngx.shared.DICT • The size of each dictionary is specified in the config file and can not be changed
- 162. Wiola: Runtime storage options 38 • Global variables in memory • are created every time on request handler • problems with concurrent requests • Module variables loaded in init_by_lua • You can read in all workers • But the write, thanks to CoW, will create a copy of the module for the VM • ngx.shared.DICT • The size of each dictionary is specified in the config file and can not be changed External storage: Redis, Memcache, PostgreSQL, MySQL and others
- 165. Wiola: Особенности. lua_code_cache 39 • lua_code_cache off; • it is convenient to debug the code
- 166. Wiola: Особенности. lua_code_cache 39 • lua_code_cache off; • it is convenient to debug the code • every require() is executed again in each request
- 167. Wiola: Особенности. lua_code_cache 39 • lua_code_cache off; • it is convenient to debug the code • every require() is executed again in each request • Even the modules loaded into init_by_lua are re-executed
- 168. Wiola: Особенности. lua_code_cache 39 • lua_code_cache off; • it is convenient to debug the code • every require() is executed again in each request • Even the modules loaded into init_by_lua are re-executed • lua_code_cache on;
- 169. Wiola: Особенности. lua_code_cache 39 • lua_code_cache off; • it is convenient to debug the code • every require() is executed again in each request • Even the modules loaded into init_by_lua are re-executed • lua_code_cache on; • for production environment
- 170. Wiola: Особенности. lua_code_cache 39 • lua_code_cache off; • it is convenient to debug the code • every require() is executed again in each request • Even the modules loaded into init_by_lua are re-executed • lua_code_cache on; • for production environment • each require() is executed once and is cached
- 171. Wiola: Особенности. lua_code_cache 39 • lua_code_cache off; • it is convenient to debug the code • every require() is executed again in each request • Even the modules loaded into init_by_lua are re-executed • lua_code_cache on; • for production environment • each require() is executed once and is cached • whenever you change the code, you need to reload nginx
- 175. Wiola: Publication in luarocks, opm 40 • luarocks: there is one part of the dependencies, there is no other: - lua-resty-websocket - lua-resty-redis
- 176. Wiola: Publication in luarocks, opm 40 • luarocks: there is one part of the dependencies, there is no other: - lua-resty-websocket - lua-resty-redis ✓ rapidjson
- 177. Wiola: Publication in luarocks, opm 40 • luarocks: there is one part of the dependencies, there is no other: - lua-resty-websocket - lua-resty-redis ✓ rapidjson ✓ lua-resty-hmac
- 178. Wiola: Publication in luarocks, opm 40 • luarocks: there is one part of the dependencies, there is no other: - lua-resty-websocket - lua-resty-redis ✓ rapidjson ✓ lua-resty-hmac ✓ lua-messagepack
- 179. Wiola: Publication in luarocks, opm 40 • luarocks: there is one part of the dependencies, there is no other: - lua-resty-websocket - lua-resty-redis ✓ rapidjson ✓ lua-resty-hmac ✓ lua-messagepack • opm (OpenResty Package Manager): accurate to "reverse":
- 180. Wiola: Publication in luarocks, opm 40 • luarocks: there is one part of the dependencies, there is no other: - lua-resty-websocket - lua-resty-redis ✓ rapidjson ✓ lua-resty-hmac ✓ lua-messagepack • opm (OpenResty Package Manager): accurate to "reverse": ✓ lua-resty-websocket
- 181. Wiola: Publication in luarocks, opm 40 • luarocks: there is one part of the dependencies, there is no other: - lua-resty-websocket - lua-resty-redis ✓ rapidjson ✓ lua-resty-hmac ✓ lua-messagepack • opm (OpenResty Package Manager): accurate to "reverse": ✓ lua-resty-websocket ✓ lua-resty-redis
- 182. Wiola: Publication in luarocks, opm 40 • luarocks: there is one part of the dependencies, there is no other: - lua-resty-websocket - lua-resty-redis ✓ rapidjson ✓ lua-resty-hmac ✓ lua-messagepack • opm (OpenResty Package Manager): accurate to "reverse": ✓ lua-resty-websocket ✓ lua-resty-redis - rapidjson
- 183. Wiola: Publication in luarocks, opm 40 • luarocks: there is one part of the dependencies, there is no other: - lua-resty-websocket - lua-resty-redis ✓ rapidjson ✓ lua-resty-hmac ✓ lua-messagepack • opm (OpenResty Package Manager): accurate to "reverse": ✓ lua-resty-websocket ✓ lua-resty-redis - rapidjson ✓ lua-resty-hmac
- 184. Wiola: Publication in luarocks, opm 40 • luarocks: there is one part of the dependencies, there is no other: - lua-resty-websocket - lua-resty-redis ✓ rapidjson ✓ lua-resty-hmac ✓ lua-messagepack • opm (OpenResty Package Manager): accurate to "reverse": ✓ lua-resty-websocket ✓ lua-resty-redis - rapidjson ✓ lua-resty-hmac - lua-messagepack
- 186. Useful links about WAMP • WAMP main site: http://wamp-proto.org/ • WAMP spec on github: github.com/wamp-proto/wamp-proto • Mailing list: https://groups.google.com/forum/#!forum/wampws • Wiola: https://github.com/KSDaemon/wiola • Loowy: https://github.com/KSDaemon/Loowy • Wampy.js: https://github.com/KSDaemon/wampy.js • Wiola docker image: https://hub.docker.com/r/421p/wiola/ • Crossbar Router: https://crossbar.io/ и https://demo.crossbar.io/ 41
- 187. WAMP: Conclusion 42
- 190. WAMP: Conclusion • A simple and open Protocol • RPC and PubSub in one transport/protocol • Any transport and serialization 42
- 191. WAMP: Conclusion • A simple and open Protocol • RPC and PubSub in one transport/protocol • Any transport and serialization • Allows you to build distributed applications with loosely coupled components 42
- 192. WAMP: Conclusion • A simple and open Protocol • RPC and PubSub in one transport/protocol • Any transport and serialization • Allows you to build distributed applications with loosely coupled components • There are implementations in many languages 42
- 193. WAMP: Conclusion • A simple and open Protocol • RPC and PubSub in one transport/protocol • Any transport and serialization • Allows you to build distributed applications with loosely coupled components • There are implementations in many languages • Open source 42
- 194. WAMP: Conclusion • A simple and open Protocol • RPC and PubSub in one transport/protocol • Any transport and serialization • Allows you to build distributed applications with loosely coupled components • There are implementations in many languages • Open source • A small but friendly community 42
- 195. WAMP: Conclusion 43
- 198. WAMP: Conclusion • Useful architectural solution • A great option for your IoT project! (IMHO: better than MQTT) • Try WAMP: 43
- 199. WAMP: Conclusion • Useful architectural solution • A great option for your IoT project! (IMHO: better than MQTT) • Try WAMP: • Already have nginx/openresty? — try Wiola (bit.ly/wiola-router) 43
- 200. WAMP: Conclusion • Useful architectural solution • A great option for your IoT project! (IMHO: better than MQTT) • Try WAMP: • Already have nginx/openresty? — try Wiola (bit.ly/wiola-router) • Are you using a docker? 43
- 201. WAMP: Conclusion • Useful architectural solution • A great option for your IoT project! (IMHO: better than MQTT) • Try WAMP: • Already have nginx/openresty? — try Wiola (bit.ly/wiola-router) • Are you using a docker? • docker pull 421p/wiola 43
- 202. WAMP: Conclusion • Useful architectural solution • A great option for your IoT project! (IMHO: better than MQTT) • Try WAMP: • Already have nginx/openresty? — try Wiola (bit.ly/wiola-router) • Are you using a docker? • docker pull 421p/wiola • docker pull crossbario/crossbar 43
- 203. WAMP: Conclusion • Useful architectural solution • A great option for your IoT project! (IMHO: better than MQTT) • Try WAMP: • Already have nginx/openresty? — try Wiola (bit.ly/wiola-router) • Are you using a docker? • docker pull 421p/wiola • docker pull crossbario/crossbar • WAMP client for every taste and color (wamp-proto.org/implementations/) 43
- 204. Thank you for attention! And your questions :) 44 Konstantin Burkalev • Mail: kostik@ksdaemon.ru • Twitter: @KSDaemon • GitHub: KSDaemon • Blog: blog.ksdaemon.ru • SDCast: sdcast.ksdaemon.ru