消息队列（MQ）-顺序消息全新升级

[{"settings":{},"hidden":"false","fullName":"@ali/hmod-wb-zc-jwmod-messageq-banner__0-0-2","uuid":"1271202","limitConfig":{},"version":"0.0.1","componentVersionId":306333,"name":"hmod-wb-zc-jwmod-messageq-banner__0-0-2"},{"settings":{},"hidden":"false","fullName":"@ali/hmod-wb-zc-jwmod-messageq-advantage__0-0-1","uuid":"1271204","limitConfig":{},"version":"0.0.1","componentVersionId":306335,"name":"hmod-wb-zc-jwmod-messageq-advantage__0-0-1"},{"settings":{},"hidden":"false","fullName":"@ali/hmod-wb-zc-jwmod-messageq-scene__0-0-1","uuid":"1271205","limitConfig":{},"version":"0.0.1","componentVersionId":306332,"name":"hmod-wb-zc-jwmod-messageq-scene__0-0-1"},{"settings":{},"hidden":"false","fullName":"@ali/hmod-wb-zc-jwmod-messageq-anli__0-0-1","uuid":"1271206","limitConfig":{},"version":"0.0.1","componentVersionId":306336,"name":"hmod-wb-zc-jwmod-messageq-anli__0-0-1"},{"settings":{},"hidden":"false","fullName":"@ali/hmod-wb-zc-jwmod-messageq-recommend__0-0-2","uuid":"1271208","limitConfig":{},"version":"0.0.1","componentVersionId":306334,"name":"hmod-wb-zc-jwmod-messageq-recommend__0-0-2"}]

价值：严格保序，满足业务差异化需求

类型多样

支持全局顺序以及分区顺序两种，满足业务的差异化需求。

高性能&可扩展

分区顺序在保证顺序的同时，通过分区设计提高整体并发度，具有与普通消息一致的平滑扩容能力，无严格上限。

严格保序

无论是服务上下线、扩缩容，网络不稳定等情况下，始终保证消息的严格有序，优于部分开源产品。

顺序消息的类型及适用场景

类型一：全局顺序

关于全局顺序：

对于指定的一个 Topic，所有消息按照严格的先入先出（FIFO）的顺序进行发布和消费。

适用场景

对于性能要求不高的全局性业务场景，如：证券交易平台中，同一股别的交易是全平台按照订单的创建时间顺序进行交易，则可以采用全局顺序。

类型二：分区顺序

关于分区顺序

对于指定的一个 Topic，所有消息根据 sharding key 进行区块分区。同一个分区内的消息按照严格的 FIFO 顺序进行发布和消费。

适用场景

对于性能要求高，非全局性有序，可拆分出最小有序单元的系统，如：电商系统，一个完整的订单处理流程为最小有序单元，以订单 ID 作为 sharding key，那么同一个订单相关的创建订单消息、订单支付消息、订单退款消息、订单物流消息都会按照先后顺序来发布和订阅。

{"moduleinfo":{"list_count":[{"count_phone":2,"count":2}],"tit":"客户成功：帮助客户解决业务难题，助力业务增长"},"list":[{"app":"某健康APP","logo":"https://img.alicdn.com/tfs/TB1ESfOtAvoK1RjSZFwXXciCFXa-63-64.png","info":[{"con":[{"tce_rule_count":"1","word":"自建开源消息，随着客户端数量和消息并发量的上升， 对于消息服务器的性能和稳定性要求提出了非常大的考验。1.","cwidth":"78%"},{"tce_rule_count":"1","word":"应用服务端与推送服务强耦合。当推送服务不可用时，造成整个业务系统无法推送，甚无法正常工作。2.","cwidth":"78%"},{"tce_rule_count":"1","word":"对于消息排序，不能很好地保证数据会按照特定的顺序来处理。3.","cwidth":"78%"}],"itit":"业务挑战","part":"false","tce_rule_count":"1"},{"con":[{"tce_rule_count":"1","word":"方便快捷，搭建快，稳定性高，有效保证业务稳定性与数据一致性；1.","cwidth":"78%"},{"tce_rule_count":"1","word":"零维护省去大量维护成本，可以动态增加队列，能很好满足不断变化的业务需求。2.","cwidth":"78%"}],"itit":"客户心声","part":"false","tce_rule_count":"1"}]},{"app":"某创业电商APP","logo":"https://img.alicdn.com/tfs/TB1wMjItwDqK1RjSZSyXXaxEVXa-70-64.png","info":[{"con":[{"tce_rule_count":"1","word":"传统的设计，用户的请求都会被直接写入数据库或文件中，在高并发的情形下会对服务器造成巨大的压力， 同时，网站响应速度延迟加剧，用户体验差。1.","cwidth":"78%"},{"tce_rule_count":"1","word":"未使用顺序消息时，不能很好地处理缓存和DB的一致性问题，不能很好地进行不串行处理，偶尔出现支付成功，但是下单失败的情况。2.","cwidth":"78%"}],"itit":"业务挑战","part":"false","tce_rule_count":"1"},{"con":[{"tce_rule_count":"1","word":"利用binlog同步与阿里云MQ顺序消息产品，非常轻松第解决缓存一致性问题。1.","cwidth":"78%"},{"tce_rule_count":"1","word":"相对以往通过增加服务器解决并发问题而言，消息队列MQ以极低成本，免运维、高可用等优势很好地解决也业务难题。2.","cwidth":"78%"}],"itit":"客户心声","part":"false","tce_rule_count":"1"}]}],"countinfo":{"list":{"length_pc":0,"length":0}}}

{"$env":{"JSON":{}},"$page":{"env":"production"},"$context":{"moduleinfo":{"list_count":[{"count_phone":2,"count":2}],"tit":"客户成功：帮助客户解决业务难题，助力业务增长"},"list":[{"app":"某健康APP","logo":"https://img.alicdn.com/tfs/TB1ESfOtAvoK1RjSZFwXXciCFXa-63-64.png","info":[{"con":[{"tce_rule_count":"1","word":"自建开源消息，随着客户端数量和消息并发量的上升， 对于消息服务器的性能和稳定性要求提出了非常大的考验。1.","cwidth":"78%"},{"tce_rule_count":"1","word":"应用服务端与推送服务强耦合。当推送服务不可用时，造成整个业务系统无法推送，甚无法正常工作。2.","cwidth":"78%"},{"tce_rule_count":"1","word":"对于消息排序，不能很好地保证数据会按照特定的顺序来处理。3.","cwidth":"78%"}],"itit":"业务挑战","part":"false","tce_rule_count":"1"},{"con":[{"tce_rule_count":"1","word":"方便快捷，搭建快，稳定性高，有效保证业务稳定性与数据一致性；1.","cwidth":"78%"},{"tce_rule_count":"1","word":"零维护省去大量维护成本，可以动态增加队列，能很好满足不断变化的业务需求。2.","cwidth":"78%"}],"itit":"客户心声","part":"false","tce_rule_count":"1"}]},{"app":"某创业电商APP","logo":"https://img.alicdn.com/tfs/TB1wMjItwDqK1RjSZSyXXaxEVXa-70-64.png","info":[{"con":[{"tce_rule_count":"1","word":"传统的设计，用户的请求都会被直接写入数据库或文件中，在高并发的情形下会对服务器造成巨大的压力， 同时，网站响应速度延迟加剧，用户体验差。1.","cwidth":"78%"},{"tce_rule_count":"1","word":"未使用顺序消息时，不能很好地处理缓存和DB的一致性问题，不能很好地进行不串行处理，偶尔出现支付成功，但是下单失败的情况。2.","cwidth":"78%"}],"itit":"业务挑战","part":"false","tce_rule_count":"1"},{"con":[{"tce_rule_count":"1","word":"利用binlog同步与阿里云MQ顺序消息产品，非常轻松第解决缓存一致性问题。1.","cwidth":"78%"},{"tce_rule_count":"1","word":"相对以往通过增加服务器解决并发问题而言，消息队列MQ以极低成本，免运维、高可用等优势很好地解决也业务难题。2.","cwidth":"78%"}],"itit":"客户心声","part":"false","tce_rule_count":"1"}]}],"countinfo":{"list":{"length_pc":0,"length":0}}}}

客户成功：帮助客户解决业务难题，助力业务增长