About introduce Lombok to service comb

[cherrylzhao]

Hi, all

Lombok can simplify our work for creating java entity.
Using Lombok annotation, it will enhance java byte code within compile step.
We can use @Getter @Setter @Log @RequiredArgsConstructor to define our model 
simplify.
See more detail from https://projectlombok.org 

any thought?

Re: [ANN] New ServiceComb committer: Lin Zhinan (林志南）

[Zen Lin]

Thanks to ServiceComb PPMC's trust and invitation.
I have Involved in community building of ServiceComb, and I am going keep
on work on it.
By the way, I have got lots of useful help from the articles in ASF,
something like Guide to Successful Community Building [1].
Also so many nice guys and ASF Community elites have helped me, thanks.

[1] https://incubator.apache.org/guides/community.html

Best Regards,
---
Zen Lin
zenlintechnofr...@gmail.com
Focused on Micro Service and Apache ServiceComb


Zheng Feng  于2018年8月20日周一 下午10:47写道：

> Congratulations and  welcome on board !
>
> 2018-08-20 22:33 GMT+08:00 wjm wjm :
>
> >  Congratulations ~
> >
> > 2018-08-20 17:09 GMT+08:00 bismy :
> >
> > > Congratulations & welcome to join ServiceComb
> > >
> > >
> > > -- 原始邮件 --
> > > 发件人: "willem.jiang";
> > > 发送时间: 2018年8月20日(星期一) 下午4:11
> > > 收件人: "dev";
> > >
> > > 主题: [ANN] New ServiceComb committer: Lin Zhinan (林志南）
> > >
> > >
> > >
> > > Please join me and the rest of the ServiceComb PPMC members in
> welcoming
> > > our
> > > new ServiceComb committer:  Lin Zhinan (林志南).
> > >
> > > Lin Zhinan contribute the ServiceComb since last year, you may heard
> him
> > a
> > > lot if you checkout the mailing list or attend ServiceComb offline
> meetup
> > > , and
> > > we look forward to many more contributions in the future.
> > >
> > > Congratulations to Lin Zhinan! Welcome!
> > >
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> >
>

Re?? [DISCUSS]Add a local or embedded interface to call Saga

[????????????]

sorry, the picture is a simple UML of SQLTransport


https://github.com/KomachiSion/incubator-servicecomb-saga/blob/master/docs/static_files/Transport.jpg


--  --
??: "Willem Jiang";
: 2018??8??21??(??) 10:20
??: "dev";

: Re: [DISCUSS]Add a local or embedded interface to call Saga



Yeah,  the json format of SQL Transport sounds good.
As we normally use the text in the mailing list, so please draw asiis
picture or put a permanent link in the mail for us to review.



Willem Jiang

Twitter: willemjiang
Weibo: willem

On Tue, Aug 21, 2018 at 10:11 AM,   wrote:

> I think we can extend Transport interface to a new interface named
> SQLTransport.
> the SQLTransport also include 'with' function, but the parameters only
> requires datasource/serviceName, sql and parameters.
> Users can decide how to execute the sql of the datasource/serviceName in
> their own SQLTransport implements.
>
>
> In order to invoke SQLTransport successfully, we need to modify the
> Operation, Transaction and Compensation setions of Format for matching new
> json requests.
> the new json structure is:
> {
> "policy":"",
> "requests":[
> {
> "id":"",
> "type":"SQL",
> "serviceName(or datasource)":"",
> "parents":[],
> "transaction":{
> "sql":"",
> "params":[] (or {})
> },
> "compensation":{
> "sql":"",
> "params":[] (or {})
> }
> }
> ]
> }
>
>
>
> --  --
> *??:* "Willem Jiang";
> *:* 2018??8??21??(??) 8:34
> *??:* "dev";
> *:* Re: [DISCUSS]Add a local or embedded interface to call Saga
>
> The saga patten is quite simple, if call is failed, the compensation method
> should be called.
> I know someone already provide the framework[1] with Scala to simplify the
> complex if else check.
> The PersonService and EmailService can be the remote service or local
> service.
>
> val persistInvoiceAndSendEmail: Future[Email :: Person :: HNil] = saga
>   .part[Person](PersonService.addInvoice(person, invoice), p =>
> PersonService.deleteInvoice(p, invoice))
>   .part[Email](EmailService.sendInvoice(person.email, invoice), letter
> => EmailService.sendExcuse(letter.email,
> EmailService.createExcuse(letter)))
>   .run
>
> persistInvoiceAndSendEmail.onComplete {
>   case Success(email :: person :: HNil) =>
> logger.debug("There you can manage process results")
>   case Failure(SagaFailed(message, _)) =>
> logger.error(s"One saga part has been failed due to $message")
> }
>
>
>
> [1]https://github.com/dobrynya/saga
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: willem
>
> On Mon, Aug 20, 2018 at 10:26 PM, Zheng Feng  wrote:
>
> > Thanks Willem and it is a good point here. Also I'm interesting how it
> > could be used in the local or the embedded interface ? I wonder if you
> can
> > consider the ACID transaction in this situation.
> > The Saga in my options could be more used for the distributed
> environment.
> >
> > Regard,
> > Amos
> >
> > 2018-08-20 18:00 GMT+08:00 Willem Jiang :
> >
> > > the saga-core has a transport[1] interface which could be used for the
> > > purpose, now it just have the Restful implementation.
> > > If you want to implement a RPC or some local method, you can just
> > implement
> > > the transport interface.
> > > As the saga-core using json for the invocation, you need to updated the
> > > request/response  json module[2] there.
> > >
> > > [1]
> > > https://github.com/apache/incubator-servicecomb-saga/
> > > blob/master/saga-core/src/main/java/org/apache/servicecomb/saga/core/
> > > Transport.java#L20:18
> > > [2]
> > > https://github.com/apache/incubator-servicecomb-saga/
> > > tree/master/saga-format
> > >
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: willem
> > >
> > > On Mon, Aug 20, 2018 at 5:37 PM,   wrote:
> > >
> > > > Hi, all:
> > > >
> > > >
> > > > Currently, service comb saga have implemented transaction management
> > > based
> > > > on microservice.
> > > > But in some cases, users want to use Saga with a simpler way, such as
> > > > local or embedded call.
> > > > So we want to discuss whether it is possible to extend a local or
> > > embedded
> > > > interface.
> > > > When the user implements the embedded interface and injects Saga into
> > the
> > > > native program,
> > > > Saga calls the local method directly instead of calling the
> > microservice.
> > > >
> > > >
> > > > Best Wishes & Regards
> > >
> >
>
>

Re: [DISCUSS]Add a local or embedded interface to call Saga

[Willem Jiang]

Yeah,  the json format of SQL Transport sounds good.
As we normally use the text in the mailing list, so please draw asiis
picture or put a permanent link in the mail for us to review.



Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Aug 21, 2018 at 10:11 AM, 新道场开张了  wrote:

> I think we can extend Transport interface to a new interface named
> SQLTransport.
> the SQLTransport also include 'with' function, but the parameters only
> requires datasource/serviceName, sql and parameters.
> Users can decide how to execute the sql of the datasource/serviceName in
> their own SQLTransport implements.
>
>
> In order to invoke SQLTransport successfully, we need to modify the
> Operation, Transaction and Compensation setions of Format for matching new
> json requests.
> the new json structure is:
> {
> "policy":"",
> "requests":[
> {
> "id":"",
> "type":"SQL",
> "serviceName(or datasource)":"",
> "parents":[],
> "transaction":{
> "sql":"",
> "params":[] (or {})
> },
> "compensation":{
> "sql":"",
> "params":[] (or {})
> }
> }
> ]
> }
>
>
>
> -- 原始邮件 --
> *发件人:* "Willem Jiang";
> *发送时间:* 2018年8月21日(星期二) 上午8:34
> *收件人:* "dev";
> *主题:* Re: [DISCUSS]Add a local or embedded interface to call Saga
>
> The saga patten is quite simple, if call is failed, the compensation method
> should be called.
> I know someone already provide the framework[1] with Scala to simplify the
> complex if else check.
> The PersonService and EmailService can be the remote service or local
> service.
>
> val persistInvoiceAndSendEmail: Future[Email :: Person :: HNil] = saga
>   .part[Person](PersonService.addInvoice(person, invoice), p =>
> PersonService.deleteInvoice(p, invoice))
>   .part[Email](EmailService.sendInvoice(person.email, invoice), letter
> => EmailService.sendExcuse(letter.email,
> EmailService.createExcuse(letter)))
>   .run
>
> persistInvoiceAndSendEmail.onComplete {
>   case Success(email :: person :: HNil) =>
> logger.debug("There you can manage process results")
>   case Failure(SagaFailed(message, _)) =>
> logger.error(s"One saga part has been failed due to $message")
> }
>
>
>
> [1]https://github.com/dobrynya/saga
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Aug 20, 2018 at 10:26 PM, Zheng Feng  wrote:
>
> > Thanks Willem and it is a good point here. Also I'm interesting how it
> > could be used in the local or the embedded interface ? I wonder if you
> can
> > consider the ACID transaction in this situation.
> > The Saga in my options could be more used for the distributed
> environment.
> >
> > Regard,
> > Amos
> >
> > 2018-08-20 18:00 GMT+08:00 Willem Jiang :
> >
> > > the saga-core has a transport[1] interface which could be used for the
> > > purpose, now it just have the Restful implementation.
> > > If you want to implement a RPC or some local method, you can just
> > implement
> > > the transport interface.
> > > As the saga-core using json for the invocation, you need to updated the
> > > request/response  json module[2] there.
> > >
> > > [1]
> > > https://github.com/apache/incubator-servicecomb-saga/
> > > blob/master/saga-core/src/main/java/org/apache/servicecomb/saga/core/
> > > Transport.java#L20:18
> > > [2]
> > > https://github.com/apache/incubator-servicecomb-saga/
> > > tree/master/saga-format
> > >
> > >
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Mon, Aug 20, 2018 at 5:37 PM, 新道场开张了  wrote:
> > >
> > > > Hi, all:
> > > >
> > > >
> > > > Currently, service comb saga have implemented transaction management
> > > based
> > > > on microservice.
> > > > But in some cases, users want to use Saga with a simpler way, such as
> > > > local or embedded call.
> > > > So we want to discuss whether it is possible to extend a local or
> > > embedded
> > > > interface.
> > > > When the user implements the embedded interface and injects Saga into
> > the
> > > > native program,
> > > > Saga calls the local method directly instead of calling the
> > microservice.
> > > >
> > > >
> > > > Best Wishes & Regards
> > >
> >
>
>

RE?? [DISCUSS]Add a local or embedded interface to call Saga

[????????????]

I think we can extend Transport interface to a new interface named SQLTransport.
the SQLTransport also include 'with' function, but the parameters only requires 
datasource/serviceName, sql and parameters.
Users can decide how to execute the sql of the datasource/serviceName in their 
own SQLTransport implements.





In order to invoke SQLTransport successfully, we need to modify the Operation, 
Transaction and Compensation setions of Format for matching new json requests.
the new json structure is:
{
"policy":"",
"requests":[
{
"id":"",
"type":"SQL",
"serviceName(or datasource)":"",
"parents":[],
"transaction":{
"sql":"",
"params":[] (or {})
},
"compensation":{
"sql":"",
"params":[] (or {})
}
}
]
}







--  --
??: "Willem Jiang";
: 2018??8??21??(??) 8:34
??: "dev";

: Re: [DISCUSS]Add a local or embedded interface to call Saga



The saga patten is quite simple, if call is failed, the compensation method
should be called.
I know someone already provide the framework[1] with Scala to simplify the
complex if else check.
The PersonService and EmailService can be the remote service or local
service.

val persistInvoiceAndSendEmail: Future[Email :: Person :: HNil] = saga
  .part[Person](PersonService.addInvoice(person, invoice), p =>
PersonService.deleteInvoice(p, invoice))
  .part[Email](EmailService.sendInvoice(person.email, invoice), letter
=> EmailService.sendExcuse(letter.email,
EmailService.createExcuse(letter)))
  .run

persistInvoiceAndSendEmail.onComplete {
  case Success(email :: person :: HNil) =>
logger.debug("There you can manage process results")
  case Failure(SagaFailed(message, _)) =>
logger.error(s"One saga part has been failed due to $message")
}



[1]https://github.com/dobrynya/saga


Willem Jiang

Twitter: willemjiang
Weibo: willem

On Mon, Aug 20, 2018 at 10:26 PM, Zheng Feng  wrote:

> Thanks Willem and it is a good point here. Also I'm interesting how it
> could be used in the local or the embedded interface ? I wonder if you can
> consider the ACID transaction in this situation.
> The Saga in my options could be more used for the distributed environment.
>
> Regard,
> Amos
>
> 2018-08-20 18:00 GMT+08:00 Willem Jiang :
>
> > the saga-core has a transport[1] interface which could be used for the
> > purpose, now it just have the Restful implementation.
> > If you want to implement a RPC or some local method, you can just
> implement
> > the transport interface.
> > As the saga-core using json for the invocation, you need to updated the
> > request/response  json module[2] there.
> >
> > [1]
> > https://github.com/apache/incubator-servicecomb-saga/
> > blob/master/saga-core/src/main/java/org/apache/servicecomb/saga/core/
> > Transport.java#L20:18
> > [2]
> > https://github.com/apache/incubator-servicecomb-saga/
> > tree/master/saga-format
> >
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: willem
> >
> > On Mon, Aug 20, 2018 at 5:37 PM,   wrote:
> >
> > > Hi, all:
> > >
> > >
> > > Currently, service comb saga have implemented transaction management
> > based
> > > on microservice.
> > > But in some cases, users want to use Saga with a simpler way, such as
> > > local or embedded call.
> > > So we want to discuss whether it is possible to extend a local or
> > embedded
> > > interface.
> > > When the user implements the embedded interface and injects Saga into
> the
> > > native program,
> > > Saga calls the local method directly instead of calling the
> microservice.
> > >
> > >
> > > Best Wishes & Regards
> >
>

Re: [ANN] New ServiceComb committer: Lin Zhinan (林志南）

[Zheng Feng]

Congratulations and  welcome on board !

2018-08-20 22:33 GMT+08:00 wjm wjm :

>  Congratulations ~
>
> 2018-08-20 17:09 GMT+08:00 bismy :
>
> > Congratulations & welcome to join ServiceComb
> >
> >
> > -- 原始邮件 --
> > 发件人: "willem.jiang";
> > 发送时间: 2018年8月20日(星期一) 下午4:11
> > 收件人: "dev";
> >
> > 主题: [ANN] New ServiceComb committer: Lin Zhinan (林志南）
> >
> >
> >
> > Please join me and the rest of the ServiceComb PPMC members in welcoming
> > our
> > new ServiceComb committer:  Lin Zhinan (林志南).
> >
> > Lin Zhinan contribute the ServiceComb since last year, you may heard him
> a
> > lot if you checkout the mailing list or attend ServiceComb offline meetup
> > , and
> > we look forward to many more contributions in the future.
> >
> > Congratulations to Lin Zhinan! Welcome!
> >
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
>

Re: Performance tuning of ServiceComb Saga Pack

[Zheng Feng]

I'm totally agree with @bismy and we should be very careful with these
things.

2018-08-20 11:22 GMT+08:00 bismy :

> I think async is the problem I mentioned. When the transaction is in
> progress, the transaction log is not actually persistent. And transactions
> recovery may rely on these logs.
>
>
> However, I think this is an implementation problem and maybe there need
> complicated algorithms to make sure the really important data is
> persistent.
>
>
> -- 原始邮件 --
> 发件人: "willem.jiang";
> 发送时间: 2018年8月20日(星期一) 中午11:15
> 收件人: "dev";
>
> 主题: Re: Performance tuning of ServiceComb Saga Pack
>
>
>
> We could use the async writer to store the events to the database when
> using the redis. Redis cluster has the persistent storage at the same time.
>
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Aug 20, 2018 at 11:08 AM, bismy  wrote:
>
> > One doubt about redis, maybe not correct.
> >
> >
> > For transactions persistence is very important, if we use redis, the
> > transactions may lose persistence property. Event you provide retry
> > mechanism, but how about the redis instance is restarted and memory data
> > get lost?
> >
> >
> > Do you mean that using redis clusters and sync memory data between
> > clusters and assume that clusters is high available?
> >
> >
> > -- 原始邮件 --
> > 发件人: "willem.jiang";
> > 发送时间: 2018年8月16日(星期四) 中午11:00
> > 收件人: "dev";
> >
> > 主题: Re: Performance tuning of ServiceComb Saga Pack
> >
> >
> >
> > We cannot guarantee to update the redis and DB at the same time, we can
> > just do the retry in our code.
> >
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Thu, Aug 16, 2018 at 10:29 AM, fu chengeng 
> > wrote:
> >
> > > Hi Willem
> > > why not just store  'finished transacation' data to db in a async
> way.can
> > > we guarantee update on both
> > > db and redis are success at same time when the transation is aborted?
> > > 发件人: Willem Jiang
> > > 发送时间: 8月16日星期四 09:40
> > > 主题: Re: Performance tuning of ServiceComb Saga Pack
> > > 收件人: dev@servicecomb.apache.org
> > >
> > >
> > > Hi Amos Alpha send response to the Omega once the message is updated
> into
> > > redis, then we just store the transaction events into the database in
> > async
> > > way (we don't change the states here). Current Redis cluster provides
> the
> > > persistent storage, it could reduce lot of effort of us. Now we just
> use
> > > redis as a smaller table for tracking all the unfinished transaction
> > status
> > > to get better performance. If the transaction is aborted, we can
> updated
> > > the transaction in the DB and Redis at same time, if any of those calls
> > is
> > > failed, I think we just keep trying to update the status. Willem Jiang
> > > Twitter: willemjiang Weibo: 姜宁willem On Wed, Aug 15, 2018 at 10:48 PM,
> > > Zheng Feng wrote: > Hi Willem, > > It makes sense to use the redis to
> > store
> > > the pending transactions (I assume > that you mean these are the "HOT"
> > > ones). But we could be very careful to > "write" the transaction
> status,
> > > and it should be stored in the database at > last. So I think we must
> > make
> > > sure the transaction status in the redis and > the DB is consist and we
> > > SHOULD NOT lose the any status of the transaction. > > How will you use
> > the
> > > redis and the database when storing the status of > transaction ? > 1.
> > > write to the redis and the redis will sync to the database later. if >
> > > failed, rollback the transaction. > 2. both write to the redis and the
> > > database. if any of them failed, > rollback the transaction. > > We
> need
> > > the more detail :) > > Amos > > 2018-08-15 8:48 GMT+08:00 Willem Jiang
> :
> > >
> > > > > Hi, > > > > With the help of JuZheng[1][2], we managed to deploy
> the
> > > saga-spring-demo > > into K8s and start the Jmeter tests for it. By
> > running
> > > the test for a > > while, the DB CPU usage is very high and the
> response
> > > time is up 2~3 > > seconds per call. > > > > It looks like all the
> event
> > > are stored into the database in the same > table > > and never cleaned.
> > > >
> > > Now we are thinking use redis to store the hot data (the saga
> > transaction >
> > > > which is not closed), and put the cold data (which is used for
> > auditing)
> > > > > into database. In this way it could keep the event data smaller and
> > the
> > > > > event sanner[4] can just go through the unfinished the Saga
> > > transactions > to > > fire the timeout event or the compensation event.
> > > >
> > > > > Any thought? > > > > [1]https://github.com/apache/
> > > incubator-servicecomb-saga/pull/250 > > [2]https://github.com/apache/
> > > incubator-servicecomb-saga/pull/252 > > [3] > >
> > https://github.com/apache/
> > > incubator-servicecomb-saga/ > > tree/master/saga-demo/saga-spring-demo
> >
> > > > [4] > > https://github.com/apache/incubator-servicecomb-saga/blob/
> 

Re: [DISCUSS]Add a local or embedded interface to call Saga

[Zheng Feng]

Thanks Willem and it is a good point here. Also I'm interesting how it
could be used in the local or the embedded interface ? I wonder if you can
consider the ACID transaction in this situation.
The Saga in my options could be more used for the distributed environment.

Regard,
Amos

2018-08-20 18:00 GMT+08:00 Willem Jiang :

> the saga-core has a transport[1] interface which could be used for the
> purpose, now it just have the Restful implementation.
> If you want to implement a RPC or some local method, you can just implement
> the transport interface.
> As the saga-core using json for the invocation, you need to updated the
> request/response  json module[2] there.
>
> [1]
> https://github.com/apache/incubator-servicecomb-saga/
> blob/master/saga-core/src/main/java/org/apache/servicecomb/saga/core/
> Transport.java#L20:18
> [2]
> https://github.com/apache/incubator-servicecomb-saga/
> tree/master/saga-format
>
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Aug 20, 2018 at 5:37 PM, 新道场开张了  wrote:
>
> > Hi, all:
> >
> >
> > Currently, service comb saga have implemented transaction management
> based
> > on microservice.
> > But in some cases, users want to use Saga with a simpler way, such as
> > local or embedded call.
> > So we want to discuss whether it is possible to extend a local or
> embedded
> > interface.
> > When the user implements the embedded interface and injects Saga into the
> > native program,
> > Saga calls the local method directly instead of calling the microservice.
> >
> >
> > Best Wishes & Regards
>

Re: [DISCUSS]Add a local or embedded interface to call Saga

[Willem Jiang]

the saga-core has a transport[1] interface which could be used for the
purpose, now it just have the Restful implementation.
If you want to implement a RPC or some local method, you can just implement
the transport interface.
As the saga-core using json for the invocation, you need to updated the
request/response  json module[2] there.

[1]
https://github.com/apache/incubator-servicecomb-saga/blob/master/saga-core/src/main/java/org/apache/servicecomb/saga/core/Transport.java#L20:18
[2]
https://github.com/apache/incubator-servicecomb-saga/tree/master/saga-format



Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Aug 20, 2018 at 5:37 PM, 新道场开张了  wrote:

> Hi, all:
>
>
> Currently, service comb saga have implemented transaction management based
> on microservice.
> But in some cases, users want to use Saga with a simpler way, such as
> local or embedded call.
> So we want to discuss whether it is possible to extend a local or embedded
> interface.
> When the user implements the embedded interface and injects Saga into the
> native program,
> Saga calls the local method directly instead of calling the microservice.
>
>
> Best Wishes & Regards

[DISCUSS]Add a local or embedded interface to call Saga

[????????????]

Hi, all:


Currently, service comb saga have implemented transaction management based on 
microservice.
But in some cases, users want to use Saga with a simpler way, such as local or 
embedded call.
So we want to discuss whether it is possible to extend a local or embedded 
interface.
When the user implements the embedded interface and injects Saga into the 
native program, 
Saga calls the local method directly instead of calling the microservice.


Best Wishes & Regards

??????[ANN] New ServiceComb committer: Lin Zhinan (????????

[bismy]

Congratulations & welcome to join ServiceComb


--  --
??: "willem.jiang";
: 2018??8??20??(??) 4:11
??: "dev";

: [ANN] New ServiceComb committer: Lin Zhinan (



Please join me and the rest of the ServiceComb PPMC members in welcoming our
new ServiceComb committer:  Lin Zhinan (??).

Lin Zhinan contribute the ServiceComb since last year, you may heard him a
lot if you checkout the mailing list or attend ServiceComb offline meetup , and
we look forward to many more contributions in the future.

Congratulations to Lin Zhinan! Welcome!



Willem Jiang

Twitter: willemjiang
Weibo: willem

RE: [ANN] New ServiceComb committer: Lin Zhinan (林志南）

[mahesh somalaraju]

Congratulations Lin Zhinan !!!

Thanks & Regards
Mahesh Raju S
Githubid: maheshrajus

-Original Message-
From: Willem Jiang [mailto:willem.ji...@gmail.com] 
Sent: 20 August 2018 13:41
To: dev@servicecomb.apache.org
Subject: [ANN] New ServiceComb committer: Lin Zhinan (林志南）

Please join me and the rest of the ServiceComb PPMC members in welcoming our 
new ServiceComb committer:  Lin Zhinan (林志南).

Lin Zhinan contribute the ServiceComb since last year, you may heard him a lot 
if you checkout the mailing list or attend ServiceComb offline meetup , and we 
look forward to many more contributions in the future.

Congratulations to Lin Zhinan! Welcome!



Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

答复: [ANN] New ServiceComb committer: Lin Zhinan (林志南）

[YangYongZheng]

Congratulations~


Best Regards!
YangYongZheng

-邮件原件-
发件人: Willem Jiang [mailto:willem.ji...@gmail.com] 
发送时间: 2018年8月20日 16:11
收件人: dev@servicecomb.apache.org
主题: [ANN] New ServiceComb committer: Lin Zhinan (林志南）

Please join me and the rest of the ServiceComb PPMC members in welcoming our 
new ServiceComb committer:  Lin Zhinan (林志南).

Lin Zhinan contribute the ServiceComb since last year, you may heard him a lot 
if you checkout the mailing list or attend ServiceComb offline meetup , and we 
look forward to many more contributions in the future.

Congratulations to Lin Zhinan! Welcome!



Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

Re: [ANN] New ServiceComb committer: Lin Zhinan (林志南）

[Kirin Wang]

Congratulations!

Willem Jiang  于2018年8月20日周一 下午4:11写道：

> Please join me and the rest of the ServiceComb PPMC members in welcoming
> our
> new ServiceComb committer:  Lin Zhinan (林志南).
>
> Lin Zhinan contribute the ServiceComb since last year, you may heard him a
> lot if you checkout the mailing list or attend ServiceComb offline meetup
> , and
> we look forward to many more contributions in the future.
>
> Congratulations to Lin Zhinan! Welcome!
>
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>

[ANN] New ServiceComb committer: Lin Zhinan (林志南）

[Willem Jiang]

Please join me and the rest of the ServiceComb PPMC members in welcoming our
new ServiceComb committer:  Lin Zhinan (林志南).

Lin Zhinan contribute the ServiceComb since last year, you may heard him a
lot if you checkout the mailing list or attend ServiceComb offline meetup , and
we look forward to many more contributions in the future.

Congratulations to Lin Zhinan! Welcome!



Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

Re: [DISCUSS] Heading to graduation

[Willem Jiang]

If you follow the twitter of ServiceComb, you may already know about there
are two languages (go and C#) of Saga Omega implementations[1].
It's great to see more and more users interested about ServiceComb and we
are building good eco system for the user to solve the problem in the micro
services world.

[1]https://twitter.com/ServiceComb/status/1030996830463520768


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Mon, Aug 20, 2018 at 9:51 AM, bismy  wrote:

> Great. ServiceComb is running very stable in production for several our
> customers. And The community is very open to help others to join and
> discuss microservices topics.
>
>
>
>
> -- 原始邮件 --
> 发件人: "Kirin Wang";
> 发送时间: 2018年8月15日(星期三) 下午5:35
> 收件人: "dev";
>
> 主题: Re: [DISCUSS] Heading to graduation
>
>
>
> Good thread, ServiceComb is getting more and more mature now
>
> Willem Jiang  于2018年8月15日周三 下午5:09写道：
>
> > With the ServiceComb java-chassis 1.0.0-incubating and service-center
> > 1.0.0-incubating release officially out.
> > We believe it is time to discuss what requirements remains to consider
> > graduation to the TLP.
> >
> > I just updated the ServiceComb Project Status for it:
> >
> > http://servicecomb.incubator.apache.org/
> >
> > Apache ServiceComb entered incubation in November of 2017, ServiceComb
> > community learned a lot about how to do things in Apache ways.
> > Now we are a very helpful and engaged community, ready to help on all
> > questions from the ServiceComb Community.
> > We are making consensus decisions through the discussion in the mailing
> > list and voted 3 new committers.
> > We managed delivered three round released include 5 different binary
> > release, now we can do self-driving releases in good cadence.
> >
> > Please check out the maturity assessment doc[1] for more information.
> >
> > [1]
> > https://cwiki.apache.org/confluence/display/SERVICECOMB/Apache+Maturity+
> > Model+Assessment+for+ServiceComb
> >
> > Any thoughts? And welcome advice from ServiceComb Mentors?
> >
> > Regards,
> >
> >
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> >
> > On Fri, Jul 13, 2018 at 4:16 PM, Jean-Baptiste Onofré 
> > wrote:
> >
> > > It sounds good !
> > >
> > > In the mean time, I'm moving forward on the assessment document and
> > > preparing the resolution.
> > >
> > > I will send an update during the weekend.
> > >
> > > Regards
> > > JB
> > >
> > > On 13/07/2018 09:44, Willem Jiang wrote:
> > > > Yeah, we are heading to TLP.
> > > >
> > > > Current we are planing release ServiceComb Service-Center 1.0.0,
> > > > SerivceComb Java-Chassis 1.0.0 this month.
> > > > The ServiceComb trademark transfer process looks good.
> > > > And we make consensus decisions through the discussion - vote
> process.
> > > >
> > > >
> > > > Willem Jiang
> > > >
> > > > Twitter: willemjiang
> > > > Weibo: 姜宁willem
> > > >
> > > > On Sun, Jul 8, 2018 at 1:59 PM, Jean-Baptiste Onofré <
> j...@nanthrax.net>
> > > > wrote:
> > > >
> > > >> Hi all,
> > > >>
> > > >> Last week, Willem and I had a long discussion about the status of
> the
> > > >> ServiceComb podling.
> > > >>
> > > >> IMHO, we are almost ready for graduation.
> > > >>
> > > >> We worked on the maturity assessment doc:
> > > >>
> > > >> https://cwiki.apache.org/confluence/display/
> > > SERVICECOMB/Apache+Maturity+
> > > >> Model+Assessment+for+ServiceComb
> > > >>
> > > >> So, it looks good to me, I'm doing a new pass on the assessment
> model
> > > >> providing some details on some topics, but overall good.
> > > >>
> > > >> I wanted to have your inputs about that (heading to TLP).
> > > >>
> > > >> Thoughts ?
> > > >>
> > > >> Regards
> > > >> JB
> > > >> --
> > > >> Jean-Baptiste Onofré
> > > >> jbono...@apache.org
> > > >> http://blog.nanthrax.net
> > > >> Talend - http://www.talend.com
> > > >>
> > > >
> > >
> > > --
> > > Jean-Baptiste Onofré
> > > jbono...@apache.org
> > > http://blog.nanthrax.net
> > > Talend - http://www.talend.com
> > >
> >
>