Hi, RocketMQ Community
At present, many business systems control the impact of version release through the gray scale release process, and almost all service releases will strictly go gray scale release first, and then go online after verification. gRPC and HTTP calls during Gray-scale publishing can be precisely controlled through microservice governance and gateway request headers. However, if the message gray scale scheme is not implemented, even if the current link is a gray scale link, the message transmission is still uncontrollable, may go to the gray cluster monitoring partition, may also enter the online cluster monitoring partition. Therefore, when it comes to consuming logic changes, developers need to incorporate a lot of compatibility logic into their code. Even so, these logics only ensure that new traffic does not affect the line, but they do not guarantee that gray-scale traffic precisely enters the gray-scale consumer client, so that strict gray-scale verification cannot be performed. The industry lacks perfect message gray scale solution, the existing MQ gray scale solution can not completely solve the problem of message isolation and switching interface. Therefore, it is particularly important to design a lightweight message gray scale scheme that is easy to access and controllable to upgrade. I provide a message grayscale scheme with easy access and low cost, you can see it by the link below: https://github.com/apache/rocketmq/pull/8469 https://github.com/apache/rocketmq/issues/8468 https://www.yuque.com/u2210974/zrf1wg/bgqmutg83wyeyzfq/ Please reply to this email if you have any questions Best Regards
