[ 
https://issues.apache.org/jira/browse/COMDEV-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060754#comment-17060754
 ] 

Piyush Mishra commented on COMDEV-346:
--------------------------------------

Hi,

I would like to work on this project as part of GSOC.

Thanks & Regards

Piyush

> CloudEvents support for RocketMQ
> --------------------------------
>
>                 Key: COMDEV-346
>                 URL: https://issues.apache.org/jira/browse/COMDEV-346
>             Project: Community Development
>          Issue Type: Wish
>          Components: GSoC/Mentoring ideas
>            Reporter: duheng
>            Priority: Major
>              Labels: RocketMQ, gsoc2020
>
> h3. Context
> Events are everywhere. However, event producers tend to describe events 
> differently.
> The lack of a common way of describing events means developers must 
> constantly re-learn how to consume events. This also limits the potential for 
> libraries, tooling and infrastructure to aide the delivery of event data 
> across environments, like SDKs, event routers or tracing systems. The 
> portability and productivity we can achieve from event data is hindered 
> overall.
> [CloudEvents|https://github.com/cloudevents] is a specification for 
> describing event data in common formats to provide interoperability across 
> services, platforms and systems.
> RocketMQ as an event streaming platform, also hopes to improve the 
> interoperability of different event platforms by being compatible with the 
> CloudEvents standard and supporting CloudEvents SDK. In this topic, you need 
> to improve the binding spec. and implement the RocketMQ CloudEvents 
> SDK(Java、Golang or others).
> h3. You should learn before applying for this topic
> Apache RocketMQ/Apache RocketMQ SDK/CloudEvents
> h3. Mentor
> [[email protected]|mailto:[email protected]], 
> [[email protected]|mailto:[email protected]]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to