The city-based RocketMQ active-active architecture challenges and practice in the United States and dish network

This paper finishing from Lee-like soldiers at Beijing station RocketMQ meetup share the beauty dish network using some of the ideas and experiences RocketMQ process, emphasis on practice.

Guests like Bing Lee, now at the US base dish network service platform group, responsible for MQ, distribution center and task scheduling and other basic components of development.

Today, the major share from three aspects:

  • US food network news history queue
  • Based RocketMQ we do those things
  • Selection and double-thinking city living

US food network news history queue

US history on dish network is the coexistence of multiple sets of MQ, Kafka data for large teams; NSQ and RocketMQ for online business.

Several sets of problems existing cluster:
1, high maintenance costs and resources: Kafka with Scala language, NSQ with GO language, RocketMQ Java language, higher maintenance costs, each MQ message no matter how much the amount, at least to deploy a resource cost higher.
2, poor ease of use: MQ three substantially directly out of the box, the secondary development of relatively small, service access

Guess you like

Origin yq.aliyun.com/articles/718382