Skip to content

Instantly share code, notes, and snippets.

@vkmc

vkmc/Alternative transport protocol support for Zaqar

Created October 20, 2014 01:26
Show Gist options
  • Save vkmc/f69337561466c4cf4f05 to your computer and use it in GitHub Desktop.
Save vkmc/f69337561466c4cf4f05 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Alternative transport protocol support for Zaqar
Related spec: https://review.openstack.org/#/c/122425/2/specs/kilo/define-a-wire-protocol.rst
- Websockets? http://tools.ietf.org/html/rfc6455
Pros: Persistent. Faster than HTTP. Its on port 80 (firewall friendly). There is a 'secure' version. Full duplex! Both server and client have to support them.
Cons: Inits with an HTTP handshake... so no HTTP, no Websocket. It won't fit some of the use cases (?). Only transmits text or JSON.
POC: Yes.
- Raw TCP?
Pros: UBER fast. Not tied to the web.
Cons: Lower level, harder to implement.
POC: No.
- AMQP?
Pros: Messaging standard, widely used, *fast*
Cons: Constrained behavior for our use cases.
POC: Yes.
- WAMP? http://wamp.ws/ > Crossbar.io, WAMP implementation
Pros: adds asynchronous Remote Procedure Calls and Publish & Subscribe on top of WebSocket
Cons:
POC: No.
- ZMQ?
Pros: High throughput/low latency scenarios
Cons:
POC: Ask Fla :)
Why did the ZMQ development stop?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment