Download to read offline
Uploaded byVMware Tanzu
Collaborative Applications at Scale with RSocket
The document discusses the implementation of RSocket for scalable collaborative applications, highlighting its architecture and design choices. It covers the use of WebSocket connections, backpressure management, and metrics monitoring in real-time data exchange between users. Additionally, the document outlines details on service definitions, load balancing, and autoscaling for efficient performance.
More Related Content
Similar to Collaborative Applications at Scale with RSocket
Collaborative Applications at Scale with RSocket
- 4. COLLABORATIVE APPLICATIONS AT SCALE WITH RSOCKET SergeyTselovalnikov @SerCeMan Canva
- 5. SCALE Why should youcare?
- 6.
- 7.
- 8.
- 9.
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18.
- 19.
- 20.
- 21. WebSocket Gateway Editing Channel Presenting Channel RSocketWebSocket connection
- 22.
- 23.
- 24.
- 25.
- 26.
- 27.
- 28. RSocket-Java Transport - how tosend & receive Acceptor - how to handle
- 30. public interface DuplexConnection{ Mono<Void> send(Publisher<ByteBuf> frames); Flux<ByteBuf> receive(); }
- 31. public interface DuplexConnection{ Mono<Void> send(Publisher<ByteBuf> frames); Flux<ByteBuf> receive(); } RSocket Frame RSocket Frame
- 32. class RsInterceptor implementsDuplexConnectionInterceptor { @Override public DuplexConnection apply(Type type, DuplexConnection connection) { return new InstrumentedRsConnection(type, connection); } static class InstrumentedRsConnection implements DuplexConnection { @Override public Mono<Void> send(Publisher<ByteBuf> frames) { return connection.send(Flux.from(frames) // .doOnNext(frame -> recordFrame("out", frame, connectionType))); } ... } wraps the connection record each frame
- 34.
- 35. Transport metrics NEXT NEXTNEXT COMPLETE ERROR
- 36. Transport metrics NEXT NEXTNEXT NEXT COMPLETE ERROR + CANCEL frame
- 37. Transport metrics NEXT NEXTNEXT NEXT COMPLETE ERROR + cancellation + in/out
- 38.
- 39.
- 40. Acceptor public interface RSocket{ Flux<Payload> requestChannel(Flux<Payload> incoming) { ... } } incoming messages outgoing messages
- 41. Intercepting Acceptor class ForwardingRSocketimplements RSocket { private final RSocket delegate; public ForwardingRSocket(RSocket delegate) { this.delegate = delegate; } @Override public Flux<Payload> requestChannel(Publisher<Payload> payloads) { return delegate.requestChannel(payloads); } ...
- 42. What's the latencyfor establishing a channel? Intercepting Acceptor
- 43. What's the latencyfor establishing a channel? For how long do the channels stay alive? Flux<Payload> recordSignal(Supplier<Flux<Payload>> signalProvider) { var time = Timer.start("RSOCKET_STREAM_TIMER"); return signalProvider.get().doFinally(signal -> { time.stop(); }); } Intercepting Acceptor
- 44. Logging @Override public Flux<Payload> requestChannel(Publisher<Payload>payloads) { var incoming = Flux.from(payloads) .doOnSubscribe(s -> logger.info("subscribed to incoming")) .doOnCancel(() -> logger.info("unsubscribed from incoming")) .doOnComplete(() -> logger.info("complete incoming")) .doOnError(e -> logger.info("error incoming")); var outgoing = delegate().requestChannel(incoming); return outgoing // .doOnSubscribe(s -> logger.info("subscribed to outgoing")) .doOnCancel(() -> logger.info("unsubscribed from outgoing")) .doOnComplete(() -> logger.info("complete outgoing")) .doOnError(e -> logger.info("error outgoing")); } }
- 45. Logging Caveats Sep 3,2021 @ 18:42:42.042 socket connected Sep 3, 2021 @ 18:42:42.042 socket connected Sep 3, 2021 @ 18:42:42.042 subscribed to outgoing Sep 3, 2021 @ 18:42:42.042 unsubscribed from outgoing Sep 3, 2021 @ 18:42:42.042 unsubscribed from incoming Sep 3, 2021 @ 18:42:42.042 socket closed Sep 3, 2021 @ 18:42:42.042 subscribed to outgoing Sep 3, 2021 @ 18:42:42.042 subscribed to incoming Sep 3, 2021 @ 18:42:42.042 subscribed to outgoing Sep 3, 2021 @ 18:42:42.042 socket connected Sep 3, 2021 @ 18:42:42.042 unsubscribed from incoming Sep 3, 2021 @ 18:42:42.042 socket closed Sep 3, 2021 @ 18:42:42.042 socket connected Sep 3, 2021 @ 18:42:42.042 subscribed to outgoing Sep 3, 2021 @ 18:42:42.042 unsubscribed from outgoing Sep 3, 2021 @ 18:42:42.042 socket connected Sep 3, 2021 @ 18:42:42.042 subscribed to outgoing Sep 3, 2021 @ 18:42:42.042 socket closed Sep 3, 2021 @ 18:42:42.042 socket closed Sep 3, 2021 @ 18:42:42.042 unsubscribed from incoming
- 46. Logging Caveats Sep 3,2021 @ 18:42:42.042 685424232abc socket connected Sep 3, 2021 @ 18:42:42.042 685424232def socket connected Sep 3, 2021 @ 18:42:42.042 685424232abc subscribed to outgoing Sep 3, 2021 @ 18:42:42.042 685424232def unsubscribed from outgoing Sep 3, 2021 @ 18:42:42.042 685424232abc unsubscribed from incoming Sep 3, 2021 @ 18:42:42.042 685424232ghi socket closed Sep 3, 2021 @ 18:42:42.042 685424232abc subscribed to outgoing Sep 3, 2021 @ 18:42:42.042 685424232def subscribed to incoming Sep 3, 2021 @ 18:42:42.042 685424232abc subscribed to outgoing Sep 3, 2021 @ 18:42:42.042 685424232ghi socket connected Sep 3, 2021 @ 18:42:42.042 685424232abc unsubscribed from incoming Sep 3, 2021 @ 18:42:42.042 685424232def socket closed Sep 3, 2021 @ 18:42:42.042 685424232ghi socket connected Sep 3, 2021 @ 18:42:42.042 685424232abc subscribed to outgoing Sep 3, 2021 @ 18:42:42.042 685424232ghi unsubscribed from outgoing Sep 3, 2021 @ 18:42:42.042 685424232def socket connected Sep 3, 2021 @ 18:42:42.042 685424232ghi subscribed to outgoing Sep 3, 2021 @ 18:42:42.042 685424232abc socket closed Sep 3, 2021 @ 18:42:42.042 685424232ghi socket closed Sep 3, 2021 @ 18:42:42.042 685424232abc unsubscribed from incoming
- 47. Logging Caveats if (Random.nextInt(0,1_000_000) < flags.get(SAMPLING_RATE)) { setAttribute("sampled", true) }
- 48. Service Definition service FooService{ rpc connect (stream IncomingMsg) returns (stream OutgoingMsg) { option (connectMessage) = "ConnectMsg" } } Flux<Payload> => Flux<IncomingMsg>
- 50.
- 51.
- 52. Reconnection /** * Returns aFlowable that immediately publishes the current connection * status and thereafter updates as it changes. Once a connection is in * the CLOSED or ERROR state, it may not be connected again. * Implementations must publish values per the comments on ConnectionStatus. */ connectionStatus(): Flowable<ConnectionStatus>;
- 53. Exponential backoff function backoff():() => number { let i = 0; return () => Math.pow(2, i++); } ... const next = backoff(); ... await Math.round(next() * 1000);
- 54. Jitter function backoff(): ()=> number { let i = 0; return () => Math.pow(1.5, Math.random() + i++); } ... const next = backoff(); ... await Math.round(next() * 1000);
- 55.
- 56.
- 57.
- 58.
- 59. Instance configuration Number ofopen files Low latency GC (ShenandoahGC for memory)
- 60.
- 61.
- 62.
- 63.
- 64.
- 65.
- 66.
- 67.
- 68.
- 69.
- 70.
- 71.
- 72.
- 73.
- 74.
- 75.
- 76. Healthy Healthy Healthy 50000 50000 1 var socket =healthy.stream() .filter(s -> s.availability() > 0) .min(s -> s.openChannels());
- 77. Availability /** * @return apositive number representing the availability of the entity. * Higher is better, 0.0 means not available */ double availability(); 0 1 warm up
- 78. Healthy Healthy Healthy 50000 50000 1 var socket =healthy.stream() .filter(s -> s.availability() > 0) .min(s -> { var active = s.activeChannels(); var availability = s.availability(); return active / availability; });
- 79.
- 80. Autoscaling target Primary: thenumber of connections
- 81. Autoscaling target Primary: thenumber of connections
- 82. Autoscaling target Primary: thenumber of connections Secondary: CPU
- 83.
- 84.
- 85.
- 87.
- 88.
- 89.