Kuiperbelt - Asynchronous protocol proxy

Transcript

1. Kuiperbelt Asynchronous protocol proxy for prefork backend.
2. Who am I ? • twitter: @mackee_w • PAUSE ID: MACOPY • github: github.com/mackee • Yokohama.pm Co-mainterner(?)
3. What’s kuiperbelt? • Asynchronous protocol =WebSocket • Other protocols(not implement): • HTTP2 MQTT memd(!?) etc…
4. What’s kuiperbelt? • kuiperbelt is… • WebSocket to HTTP1.x converter • proxy, authentication mechanism and connection pooling
5. Motivation • Prefork(or blocking/synchronous) server has a problem of about using websocket protocol. • Problems: • C10k • AnyEvent(Perl)/Eventmachine(Ruby) -> RDB Transaction • shared connection -> sticky session(?)
6. Conventional solution • Switch to a language that support concurrent • code to trash!!! oh!!!! • pray and close eyes • C10k???? my code is not graceful but working now.
7. OTOH, Realtime application age • Server-side push • realtime paging???? huh????? • Planner’s imagination is infinite.
8. kuiperbelt flow: connection
9. Kuiperbelt flow: connection client kuipetbelt backend
10. Kuiperbelt flow: connection client kuipetbelt backend GET /connect
 with Upgrade
11. Kuiperbelt flow: connection client kuipetbelt backend proxy to endpoint
12. Kuiperbelt flow: connection client kuipetbelt backend authentication proxy query string and header
13. Kuiperbelt flow: connection client kuipetbelt backend response
 with session key header
14. Kuiperbelt flow: connection client kuipetbelt backend register session key
15. Kuiperbelt flow: connection client kuipetbelt backend upgrade to websocket
16. Kuiperbelt flow: server-side push
17. Kuiperbelt flow: server-side push client kuipetbelt backend POST /send with session key header
18. Kuiperbelt flow: server-side push client kuipetbelt backend search session by key
19. Kuiperbelt flow: server-side push client kuipetbelt backend write body to connection
20. other features • server-side closing with message • close callback to backend by client- side normally closing • switch binary/text frame
21. clusters • kuiperbelt is support single host application only. • But does not mean there is no way. • Kuiperbelt server host name in header of /connect callback. • If you want to connection mapping to some kuiperbelt host, store this hostname in datastore.
22. implementation plan • (really) cluster support • Redis Pub/Sub or MQTT backbone • DHT and sticky session? • documentation (oh…
23. Please try it!!! github.com/mackee/kuiperbelt
24. Thank you!