I would suggest preparing wiki for each new major functionality with a short
description of what has to be achieved and how.Discussions can be done in the
mailing lists after everyone understands the issue, and summary of goals and
design decisions at wiki will give a quick idea about the feature for everyone
who joins the project (and have ideas on how to improve).
Roman
On Saturday, February 25, 2017 9:50 AM, Willem Jiang
<[email protected]> wrote:
Hi yukon,
This roadmap looks good, can we put it into the incubation site?
We can let more people know about our roadmap even he doesn't subscribe the
dev mailing list.
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Fri, Feb 24, 2017 at 10:54 PM, yukon <[email protected]> wrote:
> Dear all，
>
> The RocketMQ 4.0.0-incubating has been released last week, it's time to
> discuss the new feature roadmap of RocketMQ 4.x.
>
> We have carried out a preliminary feature programming for RocketMQ 4.x,
> hope this email has broached the subject and get more feedbacks from
> RocketMQ community.
>
> 4.1.0~4.3.0-incubating RoadMap:
>
> 1. Define a vendor independent new messaging standards for developers api,
> and give a default implementation of RocketMQ.[1]
> 2. Define and implement a reasonable filter language based on a subset of
> the SQL 92 expression syntax to support message filtering.
> 3. Support batch messaging, let RocketMQ can handle millions of small
> messages.[2]
> 4. Support consistent hash allocate strategy in consumer load balancing.[3]
> 5. A new global order message mechanism, without hot-points problem.
> 6. Support distributed transaction messaging.
> 7. A strict, non-redundant message delivery mechanism.
> 8. A multi-replication high availability／reliability mechanism, without
> human intervention.
> 9. Provide docker image for easy deployment and management, optimize for
> the latest version.
> 10. Support message queuing telemetry transport(MQTT).
>
> 4.4.0-incubating+ RoadMap:
>
> 1. Support more application layer protocol: WebSocket, HTTP2, etc.
> 2. Support more native language SDK: PHP, Python, .Net, Node, Go, etc. The
> chosen programming languages are the result of surveying many cloud
> platforms.
> 3. Support advanced message queuing protocol(AMQP).
>
> RocketMQ-externals:
>
> 1. rocketmq-console, provide a ops dashboard for RocketMQ.[4]
> 2. rocketmq-jms, provide a new client to support JMS 2.0.[5]
> 3. rocketmq-flume-ng, integrate RocketMQ with Apache Flume.[6][6-1]
> 4. rocketmq-storm, integrate RocketMQ with storm.[7]
> 5. rocketmq-ignite, integrate RocketMQ with ignite.[8][9]
> 6. rocketmq-spark, integrate RocketMQ with spark.[10]
> 7. rocketmq-flink, integrate RocketMQ with flink.[11]
> 8. rocketmq-distributedlog integrate RocketMQ with distributedlog.[12]
> 9. rocketmq-spring, provide a adapter for spring and spring-boot.
>
> Above mentioned are in the planning, any advice or contribution are
> welcome.
>
> Thanks,
> yukon
>
> [1]. https://issues.apache.org/jira/browse/ROCKETMQ-17
> [2]. https://github.com/apache/incubator-rocketmq/pull/53
> [3]. https://github.com/apache/incubator-rocketmq/pull/67
> [4]. https://github.com/rocketmq/rocketmq-console-ng
> [5]. https://github.com/rocketmq/rocketmq-jms
> [6]. https://github.com/rocketmq/rocketmq-flume-ng
> [6-1]. https://issues.apache.org/jira/browse/FLUME-3058
> [7]. https://github.com/rocketmq/rocketmq-storm
> [8]. https://issues.apache.org/jira/browse/ROCKETMQ-41
> [9]. https://issues.apache.org/jira/browse/IGNITE-4539
> [10]. https://issues.apache.org/jira/browse/ROCKETMQ-81
> [11]. https://issues.apache.org/jira/browse/ROCKETMQ-82
> [12]. https://issues.apache.org/jira/browse/ROCKETMQ-21
>
