You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@rocketmq.apache.org by heng du <du...@gmail.com> on 2018/12/06 11:03:42 UTC
[DISCUSS]The graduation of RocketMQ-Spring-Boot
Hello RocketMQ Community,
This is the discussion for the graduation of RocketMQ’s Spring Boot client(
https://github.com/apache/rocketmq-spring).
RocketMQ-spring-boot provides a kind of Spring-style usage of a client of
Apache RocketMQ, which makes RocketMQ native API transparent with the
Spring-Messaging API and takes advantage of Spring annotation and
auto-configure. It uses the RocketMQTemplate API to send spring standard
messages to RocketMQ Broker as well as uses implementation class which
annotated by RocketMQListener to receive messages.
After more than 6 months of incubation, the RocketMQ-spring-boot project
has been used by several companies and main features have been verified in
their production environment, and up to now, there are 3 active
contributors from 3 organizations in the community.
So we think it has reached the graduation standard, but in order to ensure
the quality of the project, we still investigated the usage information of
three companies from different industries, the information shows below:
1. An education company
1）Environment Configuration：
CentOS 7.x
2) Functions
Asynchronous transmission
Synchronous transmission
Orderly transmission
oneway transmission
PushConsumer with cluster mode
PushConsumer orderly
3）Business scale
100 million per day
4）scene
Mainly used for system decoupling
5) How long has it been used?
6 month
6）feedback
a) It is so convenient to use less code and configuration than
traditional API
b) Out of the box to use the spring-starter
2. A financial company
1）Environment Configuration：
（1）CentOS 6.x
（2） 3 broker nodes
2) Functions
Asynchronous transmission
PushConsumer with cluster mode
PushConsumer with broadcasting mode
3）Business scale
N/A
4）scene
Mainly used for system decoupling, message reliability assurance,
resolving to write speed mismatch between redis and Oracle scenarios.
5) How long has it been used?
2 months
6）Usage description
（1）Totally use the starter functions to send and receive the message
and verified our required scenarios.
（2）we mainly use the starter as a PoC in the current phase, will
normally use it in the next phase and production release.
3. An intelligent device company
1）Environment Configuration：
CentOS 7.4 + RocketMQ 4.3
2) Functions
Asynchronous transmission
Synchronous transmission
Orderly transmission
oneway transmission
PushConsumer with cluster mode
PushConsumer orderly
Send the message in Transaction
Consume transactional message
3）Business scale
More than 100 thousand per day, ~100B per message
4）scene
Mainly used for system decoupling
5) How long has it been used?
N/A
6）feedback
a) It is quite normal to send and receive messages, no error and
exception occur.
b) The starter is simple and convenient to use. It is compatible with
Spring ECO system and useless code and configure to performance the client
functions.
If you have any suggestion about the graduation of the RocketMQ Spring Boot
client, please feel free to reply to this email, we sincerely hope to get
your advice.
Re: [DISCUSS]The graduation of RocketMQ-Spring-Boot
Posted by Gosling Von <fe...@gmail.com>.
Glad to see the spring project be more maturity, it was with even greater delight that I also participate the review with spring community guys, really learn more from the spring code geeks.
I support graduation. From the known data, no doubt about it that this project has met the healthy community requirement and really collect some use cases from production environment.
Best Regards,
Von Gosling
> 在 2018年12月6日，下午7:03，heng du <du...@gmail.com> 写道：
>
> Hello RocketMQ Community,
>
> This is the discussion for the graduation of RocketMQ’s Spring Boot client(https://github.com/apache/rocketmq-spring <https://github.com/apache/rocketmq-spring>).
>
> RocketMQ-spring-boot provides a kind of Spring-style usage of a client of Apache RocketMQ, which makes RocketMQ native API transparent with the Spring-Messaging API and takes advantage of Spring annotation and auto-configure. It uses the RocketMQTemplate API to send spring standard messages to RocketMQ Broker as well as uses implementation class which annotated by RocketMQListener to receive messages.
>
> After more than 6 months of incubation, the RocketMQ-spring-boot project has been used by several companies and main features have been verified in their production environment, and up to now, there are 3 active contributors from 3 organizations in the community.
>
> So we think it has reached the graduation standard, but in order to ensure the quality of the project, we still investigated the usage information of three companies from different industries, the information shows below:
>
> 1. An education company
> 1）Environment Configuration：
> CentOS 7.x
> 2) Functions
> Asynchronous transmission
> Synchronous transmission
> Orderly transmission
> oneway transmission
> PushConsumer with cluster mode
> PushConsumer orderly
> 3）Business scale
> 100 million per day
> 4）scene
> Mainly used for system decoupling
> 5) How long has it been used?
> 6 month
> 6）feedback
> a) It is so convenient to use less code and configuration than traditional API
> b) Out of the box to use the spring-starter
>
> 2. A financial company
> 1）Environment Configuration：
> （1）CentOS 6.x
> （2） 3 broker nodes
> 2) Functions
> Asynchronous transmission
> PushConsumer with cluster mode
> PushConsumer with broadcasting mode
> 3）Business scale
> N/A
> 4）scene
> Mainly used for system decoupling, message reliability assurance, resolving to write speed mismatch between redis and Oracle scenarios.
> 5) How long has it been used?
> 2 months
> 6）Usage description
> （1）Totally use the starter functions to send and receive the message and verified our required scenarios.
> （2）we mainly use the starter as a PoC in the current phase, will normally use it in the next phase and production release.
>
> 3. An intelligent device company
> 1）Environment Configuration：
> CentOS 7.4 + RocketMQ 4.3
> 2) Functions
> Asynchronous transmission
> Synchronous transmission
> Orderly transmission
> oneway transmission
> PushConsumer with cluster mode
> PushConsumer orderly
> Send the message in Transaction
> Consume transactional message
> 3）Business scale
> More than 100 thousand per day, ~100B per message
> 4）scene
> Mainly used for system decoupling
> 5) How long has it been used?
> N/A
> 6）feedback
> a) It is quite normal to send and receive messages, no error and exception occur.
> b) The starter is simple and convenient to use. It is compatible with Spring ECO system and useless code and configure to performance the client functions.
>
> If you have any suggestion about the graduation of the RocketMQ Spring Boot client, please feel free to reply to this email, we sincerely hope to get your advice.
Re: [DISCUSS]The graduation of RocketMQ-Spring-Boot
Posted by Francis Lee <fr...@outlook.com>.
great. Hope it come soon
在 2018年12月6日，下午7:30，liqipeng <wl...@163.com>> 写道：
Very good news,RocketMQ’s Spring Boot client makes easier to use rockemtq. I'm looking forward to graduating as soon as possible.
在 2018年12月6日，下午7:08，Kevin Wang <wi...@gmail.com>> 写道：
very glad to hear that. Thanks every contributors and users/companies for helping the project grow up :-)
BTW, we highly appreciate the Spring Cloud team for providing detailed review and constructive feedback with the Spring standard during the graduation period.
Regards,
walking98 Kevin
在 2018年12月6日，下午7:03，heng du <du...@gmail.com>> 写道：
Hello RocketMQ Community,
This is the discussion for the graduation of RocketMQ’s Spring Boot client(https://github.com/apache/rocketmq-spring).
RocketMQ-spring-boot provides a kind of Spring-style usage of a client of Apache RocketMQ, which makes RocketMQ native API transparent with the Spring-Messaging API and takes advantage of Spring annotation and auto-configure. It uses the RocketMQTemplate API to send spring standard messages to RocketMQ Broker as well as uses implementation class which annotated by RocketMQListener to receive messages.
After more than 6 months of incubation, the RocketMQ-spring-boot project has been used by several companies and main features have been verified in their production environment, and up to now, there are 3 active contributors from 3 organizations in the community.
So we think it has reached the graduation standard, but in order to ensure the quality of the project, we still investigated the usage information of three companies from different industries, the information shows below:
1. An education company
1）Environment Configuration：
CentOS 7.x
2) Functions
Asynchronous transmission
Synchronous transmission
Orderly transmission
oneway transmission
PushConsumer with cluster mode
PushConsumer orderly
3）Business scale
100 million per day
4）scene
Mainly used for system decoupling
5) How long has it been used?
6 month
6）feedback
a) It is so convenient to use less code and configuration than traditional API
b) Out of the box to use the spring-starter
2. A financial company
1）Environment Configuration：
（1）CentOS 6.x
（2） 3 broker nodes
2) Functions
Asynchronous transmission
PushConsumer with cluster mode
PushConsumer with broadcasting mode
3）Business scale
N/A
4）scene
Mainly used for system decoupling, message reliability assurance, resolving to write speed mismatch between redis and Oracle scenarios.
5) How long has it been used?
2 months
6）Usage description
（1）Totally use the starter functions to send and receive the message and verified our required scenarios.
（2）we mainly use the starter as a PoC in the current phase, will normally use it in the next phase and production release.
3. An intelligent device company
1）Environment Configuration：
CentOS 7.4 + RocketMQ 4.3
2) Functions
Asynchronous transmission
Synchronous transmission
Orderly transmission
oneway transmission
PushConsumer with cluster mode
PushConsumer orderly
Send the message in Transaction
Consume transactional message
3）Business scale
More than 100 thousand per day, ~100B per message
4）scene
Mainly used for system decoupling
5) How long has it been used?
N/A
6）feedback
a) It is quite normal to send and receive messages, no error and exception occur.
b) The starter is simple and convenient to use. It is compatible with Spring ECO system and useless code and configure to performance the client functions.
If you have any suggestion about the graduation of the RocketMQ Spring Boot client, please feel free to reply to this email, we sincerely hope to get your advice.
Re: [DISCUSS]The graduation of RocketMQ-Spring-Boot
Posted by liqipeng <wl...@163.com>.
Very good news,RocketMQ��s Spring Boot client makes easier to use rockemtq. I'm looking forward to graduating as soon as possible.
> �� 2018��12��6�գ�����7:08��Kevin Wang <wi...@gmail.com> д����
>
> very glad to hear that. Thanks every contributors and users/companies for helping the project grow up :-)
> BTW, we highly appreciate the Spring Cloud team for providing detailed review and constructive feedback with the Spring standard during the graduation period.
>
> Regards,
>
> walking98 Kevin
>
>> �� 2018��12��6�գ�����7:03��heng du <duhengforever@gmail.com <ma...@gmail.com>> д����
>>
>> Hello RocketMQ Community,
>>
>> This is the discussion for the graduation of RocketMQ��s Spring Boot client(https://github.com/apache/rocketmq-spring <https://github.com/apache/rocketmq-spring>).
>>
>> RocketMQ-spring-boot provides a kind of Spring-style usage of a client of Apache RocketMQ, which makes RocketMQ native API transparent with the Spring-Messaging API and takes advantage of Spring annotation and auto-configure. It uses the RocketMQTemplate API to send spring standard messages to RocketMQ Broker as well as uses implementation class which annotated by RocketMQListener to receive messages.
>>
>> After more than 6 months of incubation, the RocketMQ-spring-boot project has been used by several companies and main features have been verified in their production environment, and up to now, there are 3 active contributors from 3 organizations in the community.
>>
>> So we think it has reached the graduation standard, but in order to ensure the quality of the project, we still investigated the usage information of three companies from different industries, the information shows below:
>>
>> 1. An education company
>> 1��Environment Configuration��
>> CentOS 7.x
>> 2) Functions
>> Asynchronous transmission
>> Synchronous transmission
>> Orderly transmission
>> oneway transmission
>> PushConsumer with cluster mode
>> PushConsumer orderly
>> 3��Business scale
>> 100 million per day
>> 4��scene
>> Mainly used for system decoupling
>> 5) How long has it been used?
>> 6 month
>> 6��feedback
>> a) It is so convenient to use less code and configuration than traditional API
>> b) Out of the box to use the spring-starter
>>
>> 2. A financial company
>> 1��Environment Configuration��
>> ��1��CentOS 6.x
>> ��2�� 3 broker nodes
>> 2) Functions
>> Asynchronous transmission
>> PushConsumer with cluster mode
>> PushConsumer with broadcasting mode
>> 3��Business scale
>> N/A
>> 4��scene
>> Mainly used for system decoupling, message reliability assurance, resolving to write speed mismatch between redis and Oracle scenarios.
>> 5) How long has it been used?
>> 2 months
>> 6��Usage description
>> ��1��Totally use the starter functions to send and receive the message and verified our required scenarios.
>> ��2��we mainly use the starter as a PoC in the current phase, will normally use it in the next phase and production release.
>>
>> 3. An intelligent device company
>> 1��Environment Configuration��
>> CentOS 7.4 + RocketMQ 4.3
>> 2) Functions
>> Asynchronous transmission
>> Synchronous transmission
>> Orderly transmission
>> oneway transmission
>> PushConsumer with cluster mode
>> PushConsumer orderly
>> Send the message in Transaction
>> Consume transactional message
>> 3��Business scale
>> More than 100 thousand per day, ~100B per message
>> 4��scene
>> Mainly used for system decoupling
>> 5) How long has it been used?
>> N/A
>> 6��feedback
>> a) It is quite normal to send and receive messages, no error and exception occur.
>> b) The starter is simple and convenient to use. It is compatible with Spring ECO system and useless code and configure to performance the client functions.
>>
>> If you have any suggestion about the graduation of the RocketMQ Spring Boot client, please feel free to reply to this email, we sincerely hope to get your advice.
>
Re: [DISCUSS]The graduation of RocketMQ-Spring-Boot
Posted by Kevin Wang <wi...@gmail.com>.
very glad to hear that. Thanks every contributors and users/companies for helping the project grow up :-)
BTW, we highly appreciate the Spring Cloud team for providing detailed review and constructive feedback with the Spring standard during the graduation period.
Regards,
walking98 Kevin
> 在 2018年12月6日，下午7:03，heng du <du...@gmail.com> 写道：
>
> Hello RocketMQ Community,
>
> This is the discussion for the graduation of RocketMQ’s Spring Boot client(https://github.com/apache/rocketmq-spring <https://github.com/apache/rocketmq-spring>).
>
> RocketMQ-spring-boot provides a kind of Spring-style usage of a client of Apache RocketMQ, which makes RocketMQ native API transparent with the Spring-Messaging API and takes advantage of Spring annotation and auto-configure. It uses the RocketMQTemplate API to send spring standard messages to RocketMQ Broker as well as uses implementation class which annotated by RocketMQListener to receive messages.
>
> After more than 6 months of incubation, the RocketMQ-spring-boot project has been used by several companies and main features have been verified in their production environment, and up to now, there are 3 active contributors from 3 organizations in the community.
>
> So we think it has reached the graduation standard, but in order to ensure the quality of the project, we still investigated the usage information of three companies from different industries, the information shows below:
>
> 1. An education company
> 1）Environment Configuration：
> CentOS 7.x
> 2) Functions
> Asynchronous transmission
> Synchronous transmission
> Orderly transmission
> oneway transmission
> PushConsumer with cluster mode
> PushConsumer orderly
> 3）Business scale
> 100 million per day
> 4）scene
> Mainly used for system decoupling
> 5) How long has it been used?
> 6 month
> 6）feedback
> a) It is so convenient to use less code and configuration than traditional API
> b) Out of the box to use the spring-starter
>
> 2. A financial company
> 1）Environment Configuration：
> （1）CentOS 6.x
> （2） 3 broker nodes
> 2) Functions
> Asynchronous transmission
> PushConsumer with cluster mode
> PushConsumer with broadcasting mode
> 3）Business scale
> N/A
> 4）scene
> Mainly used for system decoupling, message reliability assurance, resolving to write speed mismatch between redis and Oracle scenarios.
> 5) How long has it been used?
> 2 months
> 6）Usage description
> （1）Totally use the starter functions to send and receive the message and verified our required scenarios.
> （2）we mainly use the starter as a PoC in the current phase, will normally use it in the next phase and production release.
>
> 3. An intelligent device company
> 1）Environment Configuration：
> CentOS 7.4 + RocketMQ 4.3
> 2) Functions
> Asynchronous transmission
> Synchronous transmission
> Orderly transmission
> oneway transmission
> PushConsumer with cluster mode
> PushConsumer orderly
> Send the message in Transaction
> Consume transactional message
> 3）Business scale
> More than 100 thousand per day, ~100B per message
> 4）scene
> Mainly used for system decoupling
> 5) How long has it been used?
> N/A
> 6）feedback
> a) It is quite normal to send and receive messages, no error and exception occur.
> b) The starter is simple and convenient to use. It is compatible with Spring ECO system and useless code and configure to performance the client functions.
>
> If you have any suggestion about the graduation of the RocketMQ Spring Boot client, please feel free to reply to this email, we sincerely hope to get your advice.
Re: [DISCUSS]The graduation of RocketMQ-Spring-Boot
Posted by Kevin Wang <wi...@gmail.com>.
very glad to hear that. Thanks every contributors and users/companies for helping the project grow up :-)
BTW, we highly appreciate the Spring Cloud team for providing detailed review and constructive feedback with the Spring standard during the graduation period.
Regards,
walking98 Kevin
> �� 2018��12��6�գ�����7:03��heng du <du...@gmail.com> д����
>
> Hello RocketMQ Community,
>
> This is the discussion for the graduation of RocketMQ��s Spring Boot client(https://github.com/apache/rocketmq-spring <https://github.com/apache/rocketmq-spring>).
>
> RocketMQ-spring-boot provides a kind of Spring-style usage of a client of Apache RocketMQ, which makes RocketMQ native API transparent with the Spring-Messaging API and takes advantage of Spring annotation and auto-configure. It uses the RocketMQTemplate API to send spring standard messages to RocketMQ Broker as well as uses implementation class which annotated by RocketMQListener to receive messages.
>
> After more than 6 months of incubation, the RocketMQ-spring-boot project has been used by several companies and main features have been verified in their production environment, and up to now, there are 3 active contributors from 3 organizations in the community.
>
> So we think it has reached the graduation standard, but in order to ensure the quality of the project, we still investigated the usage information of three companies from different industries, the information shows below:
>
> 1. An education company
> 1��Environment Configuration��
> CentOS 7.x
> 2) Functions
> Asynchronous transmission
> Synchronous transmission
> Orderly transmission
> oneway transmission
> PushConsumer with cluster mode
> PushConsumer orderly
> 3��Business scale
> 100 million per day
> 4��scene
> Mainly used for system decoupling
> 5) How long has it been used?
> 6 month
> 6��feedback
> a) It is so convenient to use less code and configuration than traditional API
> b) Out of the box to use the spring-starter
>
> 2. A financial company
> 1��Environment Configuration��
> ��1��CentOS 6.x
> ��2�� 3 broker nodes
> 2) Functions
> Asynchronous transmission
> PushConsumer with cluster mode
> PushConsumer with broadcasting mode
> 3��Business scale
> N/A
> 4��scene
> Mainly used for system decoupling, message reliability assurance, resolving to write speed mismatch between redis and Oracle scenarios.
> 5) How long has it been used?
> 2 months
> 6��Usage description
> ��1��Totally use the starter functions to send and receive the message and verified our required scenarios.
> ��2��we mainly use the starter as a PoC in the current phase, will normally use it in the next phase and production release.
>
> 3. An intelligent device company
> 1��Environment Configuration��
> CentOS 7.4 + RocketMQ 4.3
> 2) Functions
> Asynchronous transmission
> Synchronous transmission
> Orderly transmission
> oneway transmission
> PushConsumer with cluster mode
> PushConsumer orderly
> Send the message in Transaction
> Consume transactional message
> 3��Business scale
> More than 100 thousand per day, ~100B per message
> 4��scene
> Mainly used for system decoupling
> 5) How long has it been used?
> N/A
> 6��feedback
> a) It is quite normal to send and receive messages, no error and exception occur.
> b) The starter is simple and convenient to use. It is compatible with Spring ECO system and useless code and configure to performance the client functions.
>
> If you have any suggestion about the graduation of the RocketMQ Spring Boot client, please feel free to reply to this email, we sincerely hope to get your advice.
Re: [DISCUSS]The graduation of RocketMQ-Spring-Boot
Posted by Gosling Von <fe...@gmail.com>.
Glad to see the spring project be more maturity, it was with even greater delight that I also participate the review with spring community guys, really learn more from the spring code geeks.
I support graduation. From the known data, no doubt about it that this project has met the healthy community requirement and really collect some use cases from production environment.
Best Regards,
Von Gosling
> 在 2018年12月6日，下午7:03，heng du <du...@gmail.com> 写道：
>
> Hello RocketMQ Community,
>
> This is the discussion for the graduation of RocketMQ’s Spring Boot client(https://github.com/apache/rocketmq-spring <https://github.com/apache/rocketmq-spring>).
>
> RocketMQ-spring-boot provides a kind of Spring-style usage of a client of Apache RocketMQ, which makes RocketMQ native API transparent with the Spring-Messaging API and takes advantage of Spring annotation and auto-configure. It uses the RocketMQTemplate API to send spring standard messages to RocketMQ Broker as well as uses implementation class which annotated by RocketMQListener to receive messages.
>
> After more than 6 months of incubation, the RocketMQ-spring-boot project has been used by several companies and main features have been verified in their production environment, and up to now, there are 3 active contributors from 3 organizations in the community.
>
> So we think it has reached the graduation standard, but in order to ensure the quality of the project, we still investigated the usage information of three companies from different industries, the information shows below:
>
> 1. An education company
> 1）Environment Configuration：
> CentOS 7.x
> 2) Functions
> Asynchronous transmission
> Synchronous transmission
> Orderly transmission
> oneway transmission
> PushConsumer with cluster mode
> PushConsumer orderly
> 3）Business scale
> 100 million per day
> 4）scene
> Mainly used for system decoupling
> 5) How long has it been used?
> 6 month
> 6）feedback
> a) It is so convenient to use less code and configuration than traditional API
> b) Out of the box to use the spring-starter
>
> 2. A financial company
> 1）Environment Configuration：
> （1）CentOS 6.x
> （2） 3 broker nodes
> 2) Functions
> Asynchronous transmission
> PushConsumer with cluster mode
> PushConsumer with broadcasting mode
> 3）Business scale
> N/A
> 4）scene
> Mainly used for system decoupling, message reliability assurance, resolving to write speed mismatch between redis and Oracle scenarios.
> 5) How long has it been used?
> 2 months
> 6）Usage description
> （1）Totally use the starter functions to send and receive the message and verified our required scenarios.
> （2）we mainly use the starter as a PoC in the current phase, will normally use it in the next phase and production release.
>
> 3. An intelligent device company
> 1）Environment Configuration：
> CentOS 7.4 + RocketMQ 4.3
> 2) Functions
> Asynchronous transmission
> Synchronous transmission
> Orderly transmission
> oneway transmission
> PushConsumer with cluster mode
> PushConsumer orderly
> Send the message in Transaction
> Consume transactional message
> 3）Business scale
> More than 100 thousand per day, ~100B per message
> 4）scene
> Mainly used for system decoupling
> 5) How long has it been used?
> N/A
> 6）feedback
> a) It is quite normal to send and receive messages, no error and exception occur.
> b) The starter is simple and convenient to use. It is compatible with Spring ECO system and useless code and configure to performance the client functions.
>
> If you have any suggestion about the graduation of the RocketMQ Spring Boot client, please feel free to reply to this email, we sincerely hope to get your advice.