ry task
to update the cache. All interactions from Microservice to ApiManager are
done by the Task.
The ApiManager is designed to interact directly with service center as a
pure client with api inside only. Its structure is as follows:
Best Regards!Eric Lee
Hi all,
The proposal has moved to the ServiceComb website, anyone can visit it at
http://servicecomb.io/docs/service-registry-refactor-proposal/ . The
content of the it will keep up to date during this discussion.
BTW, thanks to Willem's advice.
Best Regards!
Eric Lee
2017-12-19 17:31 GMT+
another alpha may
query from database and process the same event before the timeout event
being processed by the previous alpha.
Current implementation details can move forward to
https://github.com/apache/incubator-servicecomb-saga/pull/122 .
Any suggestion is welcome.
Best Regards!
Eric Lee
all solution need import "lock";
> > > If one event can only handle by one alpha at the same time,we may need
> > > election mechanism ?
> > >
> > > -- 原始邮件 --
> > > 发件人: "Eric L
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 in
urity concerns we miss? Welcome to point them out. Thanks.
Best Regards!
Eric Lee
ess of its previous status, before that, we just query for the
current task status and save it to payloads which will be stored in alpha
and return to omega when compensation happens. In this way, we can recover
the task status to the original one.
Any idea on this is welcome. Thanks.
Best Regards!
Eric Lee
s for this or any comments for these two options are welcome.
Reference:
[1] https://www.infoq.com/presentations/saga-microservices
---
Best Regards!
Eric Lee
ts later operations.
2018-03-06 14:21 GMT+08:00 Zheng Feng :
> Can you describe the details when we doing the forward recovery currently
> please ?
>
>
>
> 2018-03-05 19:32 GMT+08:00 Eric Lee :
>
> > Hi, all
> >
> > Currently, we encounter some problems in i
thoughts?
>
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.iteye.com (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Mar 5, 2018 at 7:32 PM, Eric Lee wrote:
>
> > Hi, all
> >
> > Currently, we encount
ices
[2] https://www.cs.cornell.edu/andru/cs711/2002fa/reading/sagas.pdf
[3] https://en.wikipedia.org/wiki/ACID
[4] https://github.com/apache/incubator-servicecomb-saga
Best Regards!
Eric Lee
2018-03-09 15:59 GMT+08:00 Daniel Qian :
> Hello guys:
>
> I read the amazing blog "Eventual Data Consist
Hi, 叶祖锋
Seems like you used the wrong jar file. The executable jar file should be `
alpha/alpha-server/target/saga/alpha-server-0.1.0-exec.jar` according to
the user guide [1].
Besides, it seems there is port conflict in your log. Can you double check
if other apps is using the exact port of 8090
+1
Checked the signed keys and checksum.
Checked the demo.
Built the code from source.
All unit tests, integration tests and acceptance tests are passed.
2018-03-19 9:27 GMT+08:00 Yang Bo :
> +1
>
> Checks I've done:
>
> 1. Checked sha512sum and GPG signature.
>
> 2. Run rat without filter on s
+1
Checked the signed keys and checksum.
Checked the samples.
Built the code from source.
All unit tests, integration tests are passed.
2018-03-19 9:57 GMT+08:00 Willem Jiang :
> +1 binding.
>
> I can build the kit from source.
> I checked the staging repo by running the Company example 1.x bra
+1
Checked the signed keys and checksum.
2018-03-19 9:28 GMT+08:00 Willem Jiang :
> +1 (binding)
>
> Checked the signed Keys and checksum.
> Checked the binary with the examples.
> Run the rat to verify the License header issue.
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (Engl
+1
All samples in the kit are passed.
2018-03-22 10:43 GMT+08:00 kirin wang :
> +1
> LGTM
>
> 2018-03-22 10:42 GMT+08:00 郑扬勇 :
>
> > +1 Non Binding
> >
> > Signatures and headers are good.
> > Built the code from Release Candidate then check all samples using
> > Staging Repo.
> > Run unit te
Saga are
welcome. Thanks.
[1] https://lists.apache.org/list.html?dev@servicecomb.apach
e.org:lte=1M:a%20question%20about%20acid%20
[2] http://design.inf.usi.ch/sites/default/files/biblio/rest-tcc.pdf
Best Regards!
Eric Lee
+1
2018-04-09 18:01 GMT+08:00 Yang Bo :
> +1
>
> On Mon, Apr 9, 2018 at 5:55 PM, 李波 wrote:
>
> > +1
> >
> > Best!
> > Li Bo
> >
> >
> > 2018-04-09 13:25 GMT+08:00 Jean-Baptiste Onofré :
> >
> > > Hi,
> > >
> > > it sounds good. Unfortunately, I'm not in the area ;)
> > >
> > > I hope next time ;
Congratulations!
2018-06-08 9:39 GMT+08:00 Kirin Wang :
> Congratulations!
>
> Zen Lin 于2018年6月8日周五 上午9:38写道：
>
> > Congratulations to Zheng Yangyong.
> >
> > Best Regards,
> > ---
> > Zen Lin
> > zenlintechnofr...@gmail.com
> > Focused on Micro Service and Apache ServiceComb
> >
> > 2018-06-08
On Mon, Jun 11, 2018 at 8:51 AM, wjm wjm wrote:
> >
> > > Congratulations ~
> > >
> > > 2018-06-10 15:31 GMT+08:00 Willem Jiang :
> > >
> > > > Please join me and the rest of the ServiceComb PPMC members in
> > welcoming
> > > > our
&
Yes
Zhang Qi 於 2018年9月7日 週五 上午10:19寫道：
> yes
>
> Willem Jiang 于2018年9月6日周四 上午9:00写道：
>
> > Hi Committers
> >
> > As the discussion of "Heading to graduation" [1], we want to setup
> > the PMC as part of ServiceComb graduation resolution. So we'd like to
> > confirm whether you want to remain a
LVED, that the Apache ServiceComb Project be and hereby is
> > > responsible for the creation and maintenance of software related to a
> > > microservice framework that provides a set of tools and components to
> > > make development and deployment of cloud app
f the projects within the scope of responsibility of the Apache
> > ServiceComb Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache ServiceComb
> >
23 matches
Mail list logo
