Re: [VOTE] Release Apache RocketMQ EventBridge 1.1.0

[沈林]

Hello RocketMQ Community,

This is the vote for 1.1.0 release of Apache RocketMQ EventBridge. In this
version, We will be releasing some functionality of EventBridge. Including:
[+] The runtime of eventbridge.
[+] Built in demo use case: send events,filter,transform and write to file.
[+] Supports built-in databases without the need to build MySQL.
[+] Add file sink connector.
[+] Add e2e test case.
[+] Add git workflows check when creating the  pull request.

According to the last suggestion, a new version to be released was
generated through github workflows:

The artifact:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-eventbridge/1.1.0-rc1/


Git tag for the release:
https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.1.0

Hash for the release tag: 0008e7826f0cbf2e61f14565a5229e97be42c8d7

Relate Notes:
https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.1.0


The artifacts have been signed with Key :
F1CF7B3B63003270B3EB5B0B66BFD9C8461F1A4A, which can be found in the keys
file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS


Fill in the following:
[+]  check LICENSE, should be Apache V2
[+]  check NOTICE, should have a notice for third-party dependency if
necessary
[+]  extract the zip and check if the source version is correct
[+]  verify the asc(PGP sign),SHA512


The vote will be open for at least 72 hours or until the necessary number
of votes are reached.
Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
The Apache RocketMQ Team

沈林 <2011shen...@gmail.com> 于2024年2月18日周日 09:02写道：

> Hello RocketMQ Community,
>
> This is the vote for 1.1.0 release of Apache RocketMQ EventBridge. In this
> version, We will be releasing some functionality of EventBridge. Including:
> [+] The runtime of eventbridge.
> [+] Built in demo use case: send events,filter,transform and write to file.
> [+] Supports built-in databases without the need to build MySQL.
> [+] Add file sink connector.
> [+] Add e2e test case.
> [+] Add git workflows check when creating the  pull request.
>
> The artifact:
>
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-eventbridge/1.1.0-rc1/
>
>
> Git tag for the release:
>
> https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.1.0
>
> Hash for the release tag: 6a852f22fb55a2c8c3e80070100547eb9b1a9b51
>
> Relate Notes:
>
> https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.1.0
>
>
> The artifacts have been signed with Key :
> F1CF7B3B63003270B3EB5B0B66BFD9C8461F1A4A, which can be found in the keys
> file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
>
>
> Fill in the following:
> [+]  check LICENSE, should be Apache V2
> [+]  check NOTICE, should have a notice for third-party dependency if
> necessary
> [+]  extract the zip and check if the source version is correct
> [+]  verify the asc(PGP sign),SHA512
>
>
> The vote will be open for at least 72 hours or until the necessary number
> of votes are reached.
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Thanks,
> The Apache RocketMQ Team
>

[VOTE] Release Apache RocketMQ EventBridge 1.1.0

[沈林]

Hello RocketMQ Community,

This is the vote for 1.1.0 release of Apache RocketMQ EventBridge. In this
version, We will be releasing some functionality of EventBridge. Including:
[+] The runtime of eventbridge.
[+] Built in demo use case: send events,filter,transform and write to file.
[+] Supports built-in databases without the need to build MySQL.
[+] Add file sink connector.
[+] Add e2e test case.
[+] Add git workflows check when creating the  pull request.

The artifact:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-eventbridge/1.1.0-rc1/


Git tag for the release:
https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.1.0

Hash for the release tag: 6a852f22fb55a2c8c3e80070100547eb9b1a9b51

Relate Notes:
https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.1.0


The artifacts have been signed with Key :
F1CF7B3B63003270B3EB5B0B66BFD9C8461F1A4A, which can be found in the keys
file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS


Fill in the following:
[+]  check LICENSE, should be Apache V2
[+]  check NOTICE, should have a notice for third-party dependency if
necessary
[+]  extract the zip and check if the source version is correct
[+]  verify the asc(PGP sign),SHA512


The vote will be open for at least 72 hours or until the necessary number
of votes are reached.
Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
The Apache RocketMQ Team

[DISCUSS] [RIP-61] RocketMQ EventBridge Runtime

[沈林]

Hello RocketMQ Community:

We have plans to add Runtime to EventBridge to reduce the dependence on
external services and improve the service experience of EDA integration.

We have written the proposal, and you can see it by the link below:
https://github.com/apache/rocketmq-eventbridge/wiki/EventBridge-Runtime

Please reply to this email if you have any suggestions.

Your response would be highly appreciated.

Re: [VOTE] Release Apache RocketMQ EventBridge 1.0.0

[沈林]

Hello RocketMQ Community,

The Apache RocketMQ EventBridge vote is now closed and has passed with 4
binding +1s, 0
non-binding +1s and no 0 or -1;

Binding votes +1s:

lollipop(lolli...@apache.org)
aaronai(aaro...@apache.org)
yukon(yu...@apache.org)
Zhanhui Li(lizhan...@apache.org)

The release will be published soon.

Thanks,

Zhanhui Li  于2022年10月25日周二 13:45写道：

> +1
>
> On Tue, Oct 25, 2022 at 11:06 AM Xinyu Zhou  wrote:
>
> > +1
> >
> > Remember to copy your key to
> > https://dist.apache.org/repos/dist/release/rocketmq/KEYS when this
> release
> > is finished.
> >
> > Regards,
> >
> > On Mon, Oct 24, 2022 at 12:33 PM aaron ai  wrote:
> >
> > > +1
> > >
> > > lollipop  于2022年10月24日周一 11:16写道：
> > >
> > > > +1
> > > >
> > > > I checked:
> > > > [OK ]  Checksums and PGP signatures are valid for the source package.
> > > > [OK ]  Source code artifacts have correct names matching the current
> > > > release.
> > > > [OK ]  License and Notice are correct in the source package.
> > > >
> > > >
> > > > On Wed, Oct 19, 2022 at 6:02 PM 沈林 <2011shen...@gmail.com> wrote:
> > > >
> > > > > Hello RocketMQ Community,
> > > > >
> > > > > This is the vote for the 1.0.0 release of Apache RocketMQ
> > EventBridge.
> > > > Also
> > > > > it will be the first release of EventBridge. In this version, We
> will
> > > be
> > > > > releasing the overall functionality of EventBridge for the first
> > time.
> > > > > Including:
> > > > > 1) Lifecycle management of core resources, including EventSource,
> > > > EventBus
> > > > > and EventRule.
> > > > > 2) The event api gateway for putting the event to EventBridge.
> > > > > 3) The Source Runner and Target Runner on RocketMQ Connect.
> > > > > 4) The Source and Target class register.
> > > > > 5) The Filter and Transform RocketMQ Connect plugin, before
> > delivering
> > > > the
> > > > > event to the target.
> > > > > and so on. (Detail: https://github.com/apache/rocketmq-eventbridge
> )
> > > > >
> > > > >
> > > > > The artifact:
> > > > >
> > > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-eventbridge/1.0.0-rc1/
> > > > >
> > > > >
> > > > > Git tag for the release:
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.0.0
> > > > >
> > > > > Hash for the release tag: e11edf726ddb564c1fc4ade00fc3103c798c1291
> > > > >
> > > > > Relate Notes:
> > > > >
> > > > >
> > > >
> > >
> >
> https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.0.0
> > > > >
> > > > >
> > > > > The artifacts have been signed with Key :
> > > > > F1CF7B3B63003270B3EB5B0B66BFD9C8461F1A4A, which can be found in the
> > > keys
> > > > > file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
> > > > >
> > > > >
> > > > > Fill in the following:
> > > > > [+]  check LICENSE, should be Apache V2
> > > > > [+]  check NOTICE, should have a notice for third-party dependency
> if
> > > > > necessary
> > > > > [+]  extract the zip and check if the source version is correct
> > > > > [+]  verify the asc(PGP sign),SHA512
> > > > >
> > > > >
> > > > > The vote will be open for at least 72 hours or until the necessary
> > > number
> > > > > of votes are reached.
> > > > > Please vote accordingly:
> > > > > [ ] +1 approve
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 disapprove with the reason
> > > > >
> > > > > Thanks,
> > > > > The Apache RocketMQ Team
> > > > >
> > > >
> > >
> >
>

[VOTE] Release Apache RocketMQ EventBridge 1.0.0

[沈林]

Hello RocketMQ Community,

This is the vote for the 1.0.0 release of Apache RocketMQ EventBridge. Also
it will be the first release of EventBridge. In this version, We will be
releasing the overall functionality of EventBridge for the first time.
Including:
1) Lifecycle management of core resources, including EventSource, EventBus
and EventRule.
2) The event api gateway for putting the event to EventBridge.
3) The Source Runner and Target Runner on RocketMQ Connect.
4) The Source and Target class register.
5) The Filter and Transform RocketMQ Connect plugin, before delivering the
event to the target.
and so on. (Detail: https://github.com/apache/rocketmq-eventbridge)


The artifact:
https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-eventbridge/1.0.0-rc1/


Git tag for the release:
https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.0.0

Hash for the release tag: e11edf726ddb564c1fc4ade00fc3103c798c1291

Relate Notes:
https://github.com/apache/rocketmq-eventbridge/releases/tag/rocketmq-eventbridge-1.0.0


The artifacts have been signed with Key :
F1CF7B3B63003270B3EB5B0B66BFD9C8461F1A4A, which can be found in the keys
file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS


Fill in the following:
[+]  check LICENSE, should be Apache V2
[+]  check NOTICE, should have a notice for third-party dependency if
necessary
[+]  extract the zip and check if the source version is correct
[+]  verify the asc(PGP sign),SHA512


The vote will be open for at least 72 hours or until the necessary number
of votes are reached.
Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
The Apache RocketMQ Team

[DISCUSS] Prepare to release Apache RocketMQ EventBridge 1.0.0

[沈林]

Hello RocketMQ Community,

This is the discussion for the release of Apache RocketMQ EventBridge 1.0.0
Release.

In this version, We will be releasing the overall functionality of
EventBridge for the first time. Including:
1) Lifecycle management of core resources, including EventSource, EventBus
and EventRule.
2) The event api gatway for putting event to EventBridge.
3) The Source Runner and Target Runner on RocketMQ Connect.
4) The Source and Target class register.
5) The Filter and Transform RocketMQ Connect plugin, before delivery the
event to the target.
and so on.

Welcome everyone to comment in this email, and if no other sounds, I would
like to call for a vote for this release :-)

Regards，
LinShen

[RESULT][VOTE][RIP-38] RocketMQ EventBridge

[沈林]

Hello RocketMQ Community,

This is the vote result for the kickoff of RIP-38 《RocketMQ EventBridge》,
and it has
been passed with [4] binding +1s, [1] non-binding:

*Binding votes +1s:*
yukon(yu...@apache.org)
Xiaorui Wang(vintagew...@apache.org)
lollipop(lolli...@apache.org)
heng du(duhengfore...@apache.org)

*Non-binding votes +1s:*
aaron ai (yangkun@gmail.com)

This RIP will be accepted and its status will be updated to RocketMQ wiki
soon.

Thanks.

沈林 <2011shen...@gmail.com> 于2022年3月18日周五 11:16写道：

> Thanks for replying
>
> The relationship between rocketmq-connect and rocketmq-eventbridge is  an
> upstream and downstream.
> rocketmq-eventbridge focus on the management of events, event sources,
> targets, and establish a abstract request connect between them.  but it
> didn't establish the connection actually,
> while rocketmq-connect will do it.
>
> Best regards.
>
> dongeforever  于2022年3月14日周一 11:28写道：
>
>> The  RIP is great！
>>
>> But I still have a doubt that what's the relationship between
>> rocketmq-connect and rocketmq-eventbridge.
>>
>> Will the two projects go forward independently or be mixed together?
>>
>> The doubt does not prevent the development of rocketmq-eventbrige.
>>
>> But it is great if someone can add more explanation to it.
>>
>>
>> Xiaorui Wang  于2022年3月14日周一 10:57写道：
>>
>> > +1
>> >
>> > Best regards,
>> >
>> > Xiaorui Wang[1] - Apache RocketMQ PMC chair
>> > [1] https://github.com/vintagewang
>> >
>> >
>> > On Mon, Mar 14, 2022 at 10:40 AM aaron ai 
>> wrote:
>> >
>> > > +1
>> > >
>> > > On Mon, Mar 14, 2022 at 10:26 AM 沈林 <2011shen...@gmail.com> wrote:
>> > >
>> > > > Hi, RocketMQ Community,
>> > > >
>> > > > This is the vote for RocketMQ EventBridge, and you can read the
>> > proposal
>> > > by
>> > > > the link below:
>> > > >
>> > > >
>> > >
>> >
>> https://docs.google.com/document/d/1RWPeORHY_-ukq8qs1a1lH80fH8vSQ44U1R9xbxgEX_c/edit?usp=sharing
>> > > >
>> > > > The vote will be open for at least 72 hours or until the necessary
>> > number
>> > > > of votes are reached.
>> > > >
>> > > > Please vote accordingly:
>> > > > [ ] +1 approve
>> > > > [ ] +0 no opinion
>> > > > [ ] -1 disapprove with the reason
>> > > >
>> > > > Thanks,
>> > > > And Best Regards!
>> > > > Lin Shen 沈林
>> > > >
>> > > >
>> > > > Xiaorui Wang  于2022年3月8日周二 12:54写道：
>> > > >
>> > > > > That’s terrific! It is a milestone that greatly expands the scope
>> of
>> > > > > RocketMQ, especially on the Cloud Platform. It requires more
>> > > easy-to-use
>> > > > > capabilities of event integration. Give the thumb-up for
>> contributors
>> > > of
>> > > > > EventBridge.
>> > > > >
>> > > > > BTW, I would like to call on everyone here to pay more attention
>> to
>> > the
>> > > > > application of RocketMQ in Cloud Native. It is a
>> once-in-a-lifetime
>> > > > > opportunity for architecture upgrade.
>> > > > >
>> > > > > Cloud IaaS has uncomparable advantages over IDC IaaS. Although the
>> > > > > infrastructure software was designed by IDC 10 years ago, I
>> believe
>> > > that
>> > > > > more and more infrastructure software will be designed for Cloud
>> > > Platform
>> > > > > in the future.
>> > > > >
>> > > > > Looking forward to this technology upgrade of RocketMQ can keep
>> pace
>> > > with
>> > > > > the times.
>> > > > >
>> > > > > Cheers
>> > > > >
>> > > > > Xiaorui Wang 王小瑞
>> > > > > Apache RocketMQ PMC Chair
>> > > > >
>> > > > > On Tue, Mar 8, 2022 at 10:46 AM 沈林 <2011shen...@gmail.com> wrote:
>> > > > >
>> > > > > > Hi, RocketMQ Community:
>> > > > > >
>> > > > > > We are building a new system “rocketmq-eventbridge” based on
>> > > rocketmq,
>> > > > > > it’s an implementation of an event bus that makes it easier to
>> > build
>> > > > > > event-driven applications.
>> > > > > >
>> > > > > > We have written the proposal and you can see it by the link
>> below:
>> > > > > >
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://docs.google.com/document/d/1RWPeORHY_-ukq8qs1a1lH80fH8vSQ44U1R9xbxgEX_c/edit?usp=sharing
>> > > > > > <
>> > > > > >
>> > > > >
>> > > >
>> > >
>> >
>> https://docs.google.com/document/d/1RWPeORHY_-ukq8qs1a1lH80fH8vSQ44U1R9xbxgEX_c/edit?usp=sharing
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > > > Please reply to this email if you have any suggestions.
>> > > > >
>> > > >
>> > >
>> >
>>
>

Re: [VOTE][RIP-38] RocketMQ EventBridge

[沈林]

Thanks for replying

The relationship between rocketmq-connect and rocketmq-eventbridge is  an
upstream and downstream.
rocketmq-eventbridge focus on the management of events, event sources,
targets, and establish a abstract request connect between them.  but it
didn't establish the connection actually,
while rocketmq-connect will do it.

Best regards.

dongeforever  于2022年3月14日周一 11:28写道：

> The  RIP is great！
>
> But I still have a doubt that what's the relationship between
> rocketmq-connect and rocketmq-eventbridge.
>
> Will the two projects go forward independently or be mixed together?
>
> The doubt does not prevent the development of rocketmq-eventbrige.
>
> But it is great if someone can add more explanation to it.
>
>
> Xiaorui Wang  于2022年3月14日周一 10:57写道：
>
> > +1
> >
> > Best regards,
> >
> > Xiaorui Wang[1] - Apache RocketMQ PMC chair
> > [1] https://github.com/vintagewang
> >
> >
> > On Mon, Mar 14, 2022 at 10:40 AM aaron ai  wrote:
> >
> > > +1
> > >
> > > On Mon, Mar 14, 2022 at 10:26 AM 沈林 <2011shen...@gmail.com> wrote:
> > >
> > > > Hi, RocketMQ Community,
> > > >
> > > > This is the vote for RocketMQ EventBridge, and you can read the
> > proposal
> > > by
> > > > the link below:
> > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1RWPeORHY_-ukq8qs1a1lH80fH8vSQ44U1R9xbxgEX_c/edit?usp=sharing
> > > >
> > > > The vote will be open for at least 72 hours or until the necessary
> > number
> > > > of votes are reached.
> > > >
> > > > Please vote accordingly:
> > > > [ ] +1 approve
> > > > [ ] +0 no opinion
> > > > [ ] -1 disapprove with the reason
> > > >
> > > > Thanks,
> > > > And Best Regards!
> > > > Lin Shen 沈林
> > > >
> > > >
> > > > Xiaorui Wang  于2022年3月8日周二 12:54写道：
> > > >
> > > > > That’s terrific! It is a milestone that greatly expands the scope
> of
> > > > > RocketMQ, especially on the Cloud Platform. It requires more
> > > easy-to-use
> > > > > capabilities of event integration. Give the thumb-up for
> contributors
> > > of
> > > > > EventBridge.
> > > > >
> > > > > BTW, I would like to call on everyone here to pay more attention to
> > the
> > > > > application of RocketMQ in Cloud Native. It is a once-in-a-lifetime
> > > > > opportunity for architecture upgrade.
> > > > >
> > > > > Cloud IaaS has uncomparable advantages over IDC IaaS. Although the
> > > > > infrastructure software was designed by IDC 10 years ago, I believe
> > > that
> > > > > more and more infrastructure software will be designed for Cloud
> > > Platform
> > > > > in the future.
> > > > >
> > > > > Looking forward to this technology upgrade of RocketMQ can keep
> pace
> > > with
> > > > > the times.
> > > > >
> > > > > Cheers
> > > > >
> > > > > Xiaorui Wang 王小瑞
> > > > > Apache RocketMQ PMC Chair
> > > > >
> > > > > On Tue, Mar 8, 2022 at 10:46 AM 沈林 <2011shen...@gmail.com> wrote:
> > > > >
> > > > > > Hi, RocketMQ Community:
> > > > > >
> > > > > > We are building a new system “rocketmq-eventbridge” based on
> > > rocketmq,
> > > > > > it’s an implementation of an event bus that makes it easier to
> > build
> > > > > > event-driven applications.
> > > > > >
> > > > > > We have written the proposal and you can see it by the link
> below:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1RWPeORHY_-ukq8qs1a1lH80fH8vSQ44U1R9xbxgEX_c/edit?usp=sharing
> > > > > > <
> > > > > >
> > > > >
> > > >
> > >
> >
> https://docs.google.com/document/d/1RWPeORHY_-ukq8qs1a1lH80fH8vSQ44U1R9xbxgEX_c/edit?usp=sharing
> > > > > > >
> > > > > >
> > > > > >
> > > > > > Please reply to this email if you have any suggestions.
> > > > >
> > > >
> > >
> >
>

[VOTE][RIP-38] RocketMQ EventBridge

[沈林]

Hi, RocketMQ Community,

This is the vote for RocketMQ EventBridge, and you can read the proposal by
the link below:
https://docs.google.com/document/d/1RWPeORHY_-ukq8qs1a1lH80fH8vSQ44U1R9xbxgEX_c/edit?usp=sharing

The vote will be open for at least 72 hours or until the necessary number
of votes are reached.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Thanks,
And Best Regards!
Lin Shen 沈林


Xiaorui Wang  于2022年3月8日周二 12:54写道：

> That’s terrific! It is a milestone that greatly expands the scope of
> RocketMQ, especially on the Cloud Platform. It requires more easy-to-use
> capabilities of event integration. Give the thumb-up for contributors of
> EventBridge.
>
> BTW, I would like to call on everyone here to pay more attention to the
> application of RocketMQ in Cloud Native. It is a once-in-a-lifetime
> opportunity for architecture upgrade.
>
> Cloud IaaS has uncomparable advantages over IDC IaaS. Although the
> infrastructure software was designed by IDC 10 years ago, I believe that
> more and more infrastructure software will be designed for Cloud Platform
> in the future.
>
> Looking forward to this technology upgrade of RocketMQ can keep pace with
> the times.
>
> Cheers
>
> Xiaorui Wang 王小瑞
> Apache RocketMQ PMC Chair
>
> On Tue, Mar 8, 2022 at 10:46 AM 沈林 <2011shen...@gmail.com> wrote:
>
> > Hi, RocketMQ Community:
> >
> > We are building a new system “rocketmq-eventbridge” based on rocketmq,
> > it’s an implementation of an event bus that makes it easier to build
> > event-driven applications.
> >
> > We have written the proposal and you can see it by the link below:
> >
> >
> https://docs.google.com/document/d/1RWPeORHY_-ukq8qs1a1lH80fH8vSQ44U1R9xbxgEX_c/edit?usp=sharing
> > <
> >
> https://docs.google.com/document/d/1RWPeORHY_-ukq8qs1a1lH80fH8vSQ44U1R9xbxgEX_c/edit?usp=sharing
> > >
> >
> >
> > Please reply to this email if you have any suggestions.
>

[DISCUSS] [RIP-38] RocketMQ EventBridge

[沈林]

Hi, RocketMQ Community:

We are building a new system “rocketmq-eventbridge” based on rocketmq, it’s an 
implementation of an event bus that makes it easier to build event-driven 
applications.

We have written the proposal and you can see it by the link below:
https://docs.google.com/document/d/1RWPeORHY_-ukq8qs1a1lH80fH8vSQ44U1R9xbxgEX_c/edit?usp=sharing
 



Please reply to this email if you have any suggestions.

[DISCUSS] [RIP-38] RocketMQ EventBridge

[沈林]

Status
Current State: Proposed
Authors: shenlin, odbozhou
Shepherds: yukon, duhenglucky
Mailing List Discussion: dev@rocketmq.apache.org 

Pull Request: #PR_NUMBER
Released: 
Background & Motivation
What do we need to do
Will we add a new module?

No, we would like to add a new repo “rocketmq-eventbridge”

Will we add new APIs?

Yes, new APIs and modules will be introduced in this system

Will we add a new feature?

Yes, it is a new feature.


We are building a new system “rocketmq-eventbridge” based on rocketmq, it’s an 
implementation of an event bus that makes it easier to build event-driven 
applications.

In addition, rocketmq-eventbridge can route events between many services and 
applications based on the standard CloudEvents 1.0 specification. Users can use 
rocketmq-eventbridge to build loosely coupled and distributed event-driven 
architectures.

Why should we do that
Are there any problems with our current project?

Currently, rocketmq doesn’t support event semantics definitely, our users have 
to develop EDA applications in a traditional way. Namely, developers wrap 
events as messages and send these messages via producer, then startup a rich 
consumer client to pull messages from the broker.

What can we benefit from proposed changes?

rocketmq-eventbridge supports the CloudEvents specification natively and is 
fully compatible with their binding protocols. That means, we can easily 
integrate with the CloudEvents ecosystem.

In addition, rocketmq-eventbridge will provide many models orient EDA, like 
event source, event bus, rule, event target. Developers can create these 
resources easily and build an EDA application in a low code manner.
Goals
What problem is this proposal designed to solve?

rocketmq-eventbridge is a production solution that makes it easier to build EDA 
applications, and this project will make the rocketmq ecosystem connected with 
the cloudevents community.
Non-Goals
What problem is this proposal NOT designed to solve?

rocketmq-eventbridge is not going to replace the traditional messaging 
solution, it’s just an effective complement to asynchronous communication 
applications.
Changes
We will create a new repo `rocketmq-eventbridge` to develop this system, and it 
won’t change the rocketmq kernel. This chapter focuses on the details of 
rocketmq-eventbridge, like models, architecture, APIs, etc.
Models
rocketmq-eventbridge consists of four models.

Event source: produce and publish cloudevents to rocketmq-eventbridge.

Event bus: receive and store events from event sources. An event bus consists 
of one or more rocketmq topics.

Event rule: filter and transform events. When a matched event occurs, the event 
is routed to the event target that is associated with the event rule.

Event target: processes and consumes events in a push manner. The event target 
doesn’t need to wrap a rocketmq consumer and can be any form of consumer, for 
example, a function, a restful application, etc. 

Architecture
Events are sent to the event bus in two ways: 1) Push events through the SDK or 
Webhook actively; 2) Pulled events by eventbridge passively. Events obtained in 
both ways will be stored on the event bus. EventBus is the core concept in 
EventBridge, which allows you to subscribe to the events, filter the events, 
and push to the specified target by creating the event rule. The event on the 
event bus is stored by rocketmq. Through rocketmq-connect, we can pull the 
event from the register source to the event bus, or push the events from the 
event bus to the registered target.

Interface Design
rocketmq-eventbridge won’t change any interface or method of rocketmq kernel, 
but it will design a set of new APIs.

Type
API Name
Description
EventBus API
CreateEventBus
Create a new event bus.
GetEventBus
Get the details of the event
 bus.
DeleteEventBus
Delete the event bus.
ListEventBuses
List all the event buses.
EventSource API
CreateEventSource
Create a new event source.
UpdateEventSource
Update the event source.
DeleteEventSource
Delete the event source.
ListEventSources
List all the event sources.
ListEventTypes
List the event types of event source.
Rule API
CreateRule
Create the event rule.
GetRule
Get the details of the event rule.
EnableRule
Enable the event rule.
DisableRule
Disable the event rule.
UpdateRule
Update the details of the event rule.
DeleteRule
Delete the event rule.
ListRules
List all the event rules.
Target API
CreateTargets
Batch create targets to the specified rule
UpdateTargets
Batch update targets of  the specified rule.
DeleteTargets
Batch delete targets of the specified rule.
Data API
PutEvents
Put the events to the specified eventbus. 
CreateEventBus
Create a new event bus.
Request
URI
/bus/createEventBus

Field Name
Type
Required
Notes
Sample
Description
EventBusName
String
true
^[A-Za-z|0-9][A-Za-z|0-9|_|-]+$
Minimum length of 1. Maximum length of 127.
demo
The name of the event bus.
Description