You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicecomb.apache.org by 郑扬勇 <ya...@qq.com> on 2018/03/02 07:38:58 UTC
回复: [Please Review]New features and changes since 0.5.0 for Java Chassis
Hi,Yang Bo :
- We provide out of the box metrics support now. Prometheus and Overwatch
is supported.
Integration with Overwatch need more work for release,so Java Chassis m1 not include this feature.
Thanks & Best Regards!
------------------ 原始邮件 ------------------
发件人: "Yang Bo"<oa...@gmail.com>;
发送时间: 2018年3月1日(星期四) 下午2:22
收件人: "dev"<de...@servicecomb.apache.org>;
主题: Re: [Please Review]New features and changes since 0.5.0 for Java Chassis
Hi,
Below is the propsed release notes for Java Chassis m1. Please check.
--------------------------
Major improvements:
Java Chassis can now use Apollo as configuration center. Users can now
change configurations like load balancing policy and those changes will
come into effect on the fly.
See http://servicecomb.incubator.apache.org/users/dynamic-config/ for more
details.
Metrics was re-factored. We now uses events for collecting invocation data
instead of Hystrix. This reduces the performance penalty of computing
metrics.
Metrics can now be fetched via '/metrics' using HTTP.
See http://servicecomb.incubator.apache.org/users/metrics-in-1.0.0-m1/ for
more details.
Other Noticeable Changes:
- 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.
On Mon, Jan 29, 2018 at 4:13 PM, Eric Lee <er...@gmail.com> wrote:
> 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 <oa...@gmail.com>:
>
> > 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.
> >
>
--
Best Regards,
Yang.