Thanks for your suggestion!
I will implement DLedger Connector with
a distributed pub/sub mechanism in a separate module.
Best
Wei Liu
School of Computer Science, NWPU
????
??????????????????????
------------------ Original ------------------
From:
"dev"
<[email protected]>;
Date: Sat, Jul 9, 2022 00:26 AM
To: "dev"<[email protected]>;
Subject: Re: [Discussion] The design of EventMesh DLedger Connector
Thanks to Wei Liy for bringing this discussion.
I am +1 to this new feature, in fact, right now, we use plug-in
architecture in EventMesh, the plugin can be replaced according to the
use case, so it's great we can add a new connector plugin.
I see that you ask about combining the DLedger connector with the
standalone connector. I suggest we don't combine these, it's better to
make each plugin independent, this will make it easy to maintain the
plugin.
And furthermore, in my knowledge the DLedger is like bookKeeper? so
the new connector may implement very complex, we may need to consider
some distributed problem, but you know the standalone connector is
just want to be standalone :)
Thanks,
Wenjun
On Fri, Jul 8, 2022 at 11:51 PM ???? <[email protected]> wrote:
>
> Hi, Apache EventMesh developers.
> I'm Wei Liu, a participant in Summer2022 of OSPP
> and I come from School of CS, NWPU, China.
>
> I'm working on developing EventMesh DLedger Connector,
> whose goal is to expand the event storage component with DLedger based on
the existing API.
> The follow links is my project homepage and my rough design doc.
> Please take a look. If you have any idea or suggestion, please comment on
it.
> Hope to contribute a wonderful work to EventMesh community.
> Thanks!
>
> https://summer-ospp.ac.cn/#/org/prodetail/229020158
>
https://pasj6mrws2.feishu.cn/docx/doxcntPIZFUy00R7zq6PToKA6Vc?from=from_copylink
>
> Best
> -----------------------------------------
> Wei Liu
> School of Computer Science, NWPU
> ????
> ??????????????????????
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
