good idea, for new users, they just want to use it work well very quickly, they want to see it can produce and consume success quickly, don't want to see so many parameters, so many APIs.
At 2019-06-04 12:26:54, "heng du" <[email protected]> wrote: Dear RocketMQ Community, In order to enhance the usability of RocketMQ, a simple client API seems to be introduced into RocketMQ to further reduce the user threshold and lowering the probability of making mistakes. Compared With RocketMQ's origin client, the new client can be seen as a more high-level API that not only provides a better abstraction, but also removes some dangerous interfaces, hides more implementation details, and reduces A cumbersome configuration. At the same time, the original client will be retained as a low-level API to meet the additional needs of some experienced users, providing higher control ability for them. In the cloud-native era, messaging middleware improvements should not only be stayed in the use of cloud features (elasticity, scalability, etc.), but more importantly, it can provide users with a more concise and easy-to-use API to shield the difference brought by different cloud vendors or different deployment methods , so I think this should also be a focus of the follow-up development of RocketMQ. Looking forward to hearing your voice. Best Regards, Henry
