Hi all, The release notes for Saga 0.1.0 is as follows. Please check if there is anything missing, thanks.
Saga 0.0.1 relied heavily on the coordinator to forward requests which needs users to specify their work flow explicitly as json requests. Saga 0.1.0 uses a new architecture pack which is inspired by Zipkin. Transactions are connected by global id and identified by unique local id. In pack, alpha plays as the coordinator while omega plays as the sidecar. Implemented changes: - Omega supports to intercept ingoing/outgoing HTTP requests and inject transaction ids into request headers - Omega supports to customize compensation method by annotation - Omega supports to customize starting point of the whole transaction - Sub transactions can link as a single global transaction - Omega supports to serialize/deserialize by Kryo - Alpha supports to store transaction events permanently - Alpha is able to talk to omega through gRPC - Alpha becomes stateless to simplify alpha recovery - Acceptance tests(success, fail but compensate successfully) for the usage demo 2018-01-29 15:05 GMT+08:00 Yang Bo <[email protected]>: > Hi all, > > We'are preparing the release notes for Java Chassis 1.0.0.m1, the following > is a list of changes and features since 0.5.0. Please check whether they > are correct and supplement anything missing, thanks. > > - The Java Chassis libraries are now under group > "org.apache.servicecomb". > - We provide out of the box metrics support now. Prometheus and Overwatch > is supported. > - Configuration center was re-factored and moved out from foundation. > Support for Apollo was added. > - Users can now use Object type for calling services. > - Users can now use Generics for calling services. > - Better integration with Spring MVC. > - Upgraded to zipkin2 internally, Java Chassis can now work with zipkin > server v1 and v2. > - We are in the process of supporting reactive programming. Pojo consumer > and provider now supports CompletableFutre. > > > -- > Best Regards, > Yang. >
