1. Asynchronous and concurrent
2. Everything is flow Everything is a stream, All service structures respond in a streaming manner , Instead of just returning a single response result .
3. System health and fault tolerance , Do a lot of system health models to prevent response failure , Using heartbeat to detect component failures .
The back end is based on .NET Core Write distributed services ; Each server component is created through Docker Container deployment , Able to use Kubernetes Flexible cluster management .
Use event sourcing Achieve lasting , With Event Storage Event Store As a back-end implementation , Provides a lot of advantages , Including data elasticity and promoting state re-hydration（ Rehydration ） effect .
Multiple instances of each service are used for concurrent operation and fault tolerance . Each service instance broadcasts heartbeat , The client can switch to different instances when it can't access one of them . The same mechanism , Load balancing .
Client implementation is suitable for mainstream platforms , Including desktop browsers , OpenFin, Android, iOS, Apple Watch and WPF. be based on HTML5 Our client is using ES.next, React, Webpack, RxJs framework .
demonstration : web-demo.adaptivecluster.com/