It is completely possible to maintain API compatible while transport and codec are replaced with gRPC. However, another RIP is also proposing amendment to the existing API, with strong focus on consistency, immutability, and ease of use.
Considering the well received SemVer paradigm (see https://semver.org/), wondering that we should upgrade the major version and keep the new SDK capable of co-existence with current ones. That is, the new SDK is able to run alongside 4.x version in the same JVM, allowing partial migration to the new SDK. In the meantime, maintaining version 4.x for some time until it reached end-of-life. On Wed, Mar 9, 2022 at 1:35 PM Xiaorui Wang <[email protected]> wrote: > I think it is a right choice to support gRPC. However, I have a concern for > the client compatibility, whether the benefits of gRPC can be used by > upgrading SDK. If so, the cost of the upgrade should be taken into account. > > I look forward to receiving your reply on the questions I raised. > > Cheers > > Xiaorui Wang 王小瑞 > Apache RocketMQ PMC chair > > > On Tue, Mar 8, 2022 at 3:11 PM Zhouxiang Zhan <[email protected]> wrote: > > > Hi. RocketMQ Community: > > > > We are proposing to implement the gRPC protocol on RocketMQ. > > > > Detailed proposal: https://shimo.im/docs/gXqmeEPYgdUw5bqo/ > 「RIP-39：Support > > gRPC protocol」 > > > > Looking forward to more detailed discussions. > > >
