RSocket — new Reactive cross-network Protocol? Олег Докука и Игорь Лозинский
Download as PPTX, PDF2 likes364 views
This document summarizes a presentation about RSocket, a new reactive protocol. It discusses why RSocket was created, what RSocket is, and how to use RSocket. Specifically, it notes that RSocket aims to provide an efficient, application-level protocol that is binary, multiplexed, bidirectional, supports backpressure, and has various interaction modes like request-response, fire-and-forget, request-stream, and stream-stream. Code demos are provided to show how to use RSocket in Java, multiple languages, for RPC, and to compare it to existing solutions like gRPC and RxJava with WebSockets. In summary, RSocket is designed to save both money and time by being fast,
RSocket — new Reactive cross-network Protocol? Олег Докука и Игорь Лозинский
- 1. / by Igor Lozynskyi / by Oleh Dokuka RSocket - new Reactive-Streams protocol
- 2. 2 For whom this talk: / Reactive programmers / Protocols geeks / Curious people / We assume, you know what Reactive is
- 3. Реактивный Хардкор / Oleh Dokuka 33 Igor Lozynskyi
- 4. Oleh DokukaРеактивный Хардкор / Oleh Dokuka 44
- 6. 6 Agenda / Why RSocket? / What is RSocket? / How To RSocket?
- 11. HTTP requests
- 12. WebSockets
- 13. WebSockets
- 19. RxJava WS
- 21. Pros / Don’t care about WS / Allows seamless reactive code / Designed for streams of data
- 22. Cons / Not very resource-efficient / No Backpressure support / Have to support RxWS library: / RxWS Server / RxWS Client
- 24. 24 Binary
- 25. 25 Binary Format agnostic Massive efficient for machine to machine Built-in framing Not human readable Have to encode/decode yourself
- 26. 26 Multiplexed
- 27. STREAM BLUE STREAM YELLOW STREAM RED 27 Multiplexed
- 28. 28 Multiplexed Efficient hardware utilization Built-in logical streams within physical stream
- 30. 30 Bi-directional Client - Server just to start Built-in peer to peer communication
- 32. 32 All features of Reactive Streams Built-in signals materializing/dematerializing Reactive-Streams Backpressure
- 35. 35 Most common interaction model Useful for plain data exchange Async and multiplexed Request-Response
- 37. 37 Optimized Request-Request response Only transport delivery guaranties needed Immediately release resources Fire-and-Forget
- 39. 39 Built-in one-way streaming Backpressure support Faster Request-Stream
- 41. 41 Built-in two-way streaming Async, multiplexed (no-blocking) Channel
- 42. 42 Wide list of interaction modes Efficient solutions for most common interactions Interaction modes
- 44. Demo 44 https://github.com/netifi/rsocket-talk-demo/tree/master/demo-1-rsocket-java
- 45. Echo: 45
- 48. Hello 48
- 51. 51
- 52. 52 1 ∞
- 55. 55 GRPC Flow Control Could impact Resilience Could impact Performance
- 57. 57
- 58. 58 RSocket-RPC Flow Control Built-it Backpressure - means Resilience Pull-Push Flow control - means Performance
- 60. Demo 60
- 61. What else? 61
- 62. 62 Metadata & Payload in frame / Can send a long with message any meta info / Could be used for encoding decoding purpose
- 63. 63 Fragmentation / Any payload size / Transport take care of proper delivery by chunks
- 64. 64 Cancelation / Can safely cancel logical stream
- 65. 65 Leasing / Server can control clients requests / Preserve server stability
- 66. 66 Resumability / Designed for mobile network / Can resume streaming in case of network partitioning / disrupting
- 67. 67 Maintainers
- 68. 68 Users
- 74. 74 Summary / Is not aimed to replace but enforce
- 75. 75
- 76. 76
- 77. 77
- 78. 78
- 79. 79 Summary / Is not aimed to replace but enforce / Designed to save your money and time / Fast, low-latency, light-weight
- 80. 80 Learn more / RSocket Talk - https://bit.ly/2DUVcZ8 / RSocket Page - http://rsocket.io/