booom opened a new issue, #4144: URL: https://github.com/apache/rocketmq/issues/4144
**FEATURE REQUEST** 1. Please describe the feature you are requesting. Add feature to rocketmq-spring : QSF(queue service framework). With QSF we can produce & consume rocket-mq messages in the form of a method call, and base QSF we can implement standard MQ eventual consistency, idempotency, flow control and so on. 2. Provide any additional detail on your proposed use case for this feature. To simplify a process, we need to consider what information is essential and must be provided by users to execute this process? How to properly organize this information so that it is most user-friendly? Along this thinking path, we have extracted the necessary parameters for mq calls and organized them into the java annotations @QSFMsgProducer and @QSFMsgConsumer. After that, through the extension support of spring container in each stage of bean life cycle, we can process @QSFMsgProducer @QSFMsgConsumer annotation in BeanPostProcessor, extract method invocation information to method invocation information object MethodInvokeInfo and send it out, and locate it through MethodInvokeInfo at the message receiving endpoint. The bean where the call is made, the method where it is located, the parameters used, and then the method is called by reflection.  3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue? (1). Encapsulate mq client API to support method invoking style usage. (2). The encapsulation is easily extensible, to support idempotence/eventually consistent/ fluid control extensions and so on. (3). Isolate the mq client manage code and the business logic code, to help mq users improve their systems’ maintainability. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
