响应式云原生技术架构介绍

1、响应式云原生技术架构介绍The Reactive Cloud Native ArchitectureAgendaCloud NativeReactive programmingRSocket protocolRSocket broker1. Mission of the Cloud Native Computing Foundation.The Foundations mission is to make cloud native computing ubiquitous. The CNCF Cloud Native Definition v1.0 says:Cloud native tech

2、no logies empower organizations to build and run scalable applications in modern, dynamic environments such as public, private, and hybrid clouds. Containers, service meshes, microservices, immutable infrastructure, and declarative APls exemplify this approach.These techniques enable loosely coupled

3、 systems that are resilient, manageable, and observable. Combined with robust automation, they allow engineers to make high-impact changes frequently and p edictably with minimal toil.The Cloud Native Computing Foundation seeks to drive adoption of this paradigm by fostering and sustaining an ecosys

4、tem of open source, vendor-neutral projects. We democratize state-of-the-art patterns to make these innovations accessib le for everyone.The Reactive System - is type of the system which reacts to all the events6Reactive Manifestohttps:/Version 2.0 (September 2014)* More flexible systems*Highly resp

5、onsive*More tolerant of failures*Handling of failuresReactive StreamsA Standard for asynchronous stream processing with non-blocking back pressure* Not specifying the implementation but only the interfacesSpecification 1.0.2 (https:/announce-1.0.2)Specification 1.0.3 JVM (/announce-1.0.3)Working gro

6、ups started in 2013: Netflix, Pivotal, LightBendLatest release: August 2017Reactive Streams (continued)Keyword: Distributed architectureAll distributed operations are asynchronousWe need to stop wrapping those operations in a synchronous wayNon-Blocking mechanismsCallback-based, Rx/Reactor, Co-routi

7、nes, Async/AwaitApplication protocol that honors reactive syntaxDesigned for modern cloud applicationsProvides a standard approach to connecting and communicatingSolves problems in a consistent way across your applicationBuilt by leaders in micro-services and cloud computingRSocket Interaction Model

8、sRSocket Interaction ModelsRequest-ResponseRequestorResponderRSocket Interaction ModelsFire-and-ForgetRequestorResponderRSocket Interaction ModelsRequest-StreamRequestorResponderRSocket Interaction ModelsChannelRequestorResponderRSocket Design featuresMessage-based Binary ProtocolRequester-Responder

9、 interaction is broken down into frames that encapsulate messagesThe framing is binary (not human readable like JSON or XML)Binary is at least 30% fasterPayload AgnosticProtobuf, GraphQL, JSON, Custom BinaryMultiplexed / Connection OrientedCreates single connection between client and serverInteracti

10、ons broken into “logic streams” with an idMultiplexing solves the issue by annotating each message on the connection with astream id that partitions the connection into multiple logical streams”Logic streams and connection allow for “soft sticky” stateRSocket is Bi-DirectionalRequestorResponderResponderRequestor“Client”“Server”Single ConnectionAlibaba RSocket BrokerCentralized & SimplifiedService registryHealth checkService discoveryLoad balancingCentralized & Simplified (cont.)TracingLoggingTraffic