diff --git a/docs/distributed-system/img/mq-1.png b/docs/distributed-system/img/mq-1.png deleted file mode 100644 index a94f01e..0000000 Binary files a/docs/distributed-system/img/mq-1.png and /dev/null differ diff --git a/docs/distributed-system/img/mq-10.png b/docs/distributed-system/img/mq-10.png deleted file mode 100644 index 25aabf0..0000000 Binary files a/docs/distributed-system/img/mq-10.png and /dev/null differ diff --git a/docs/distributed-system/img/mq-11.png b/docs/distributed-system/img/mq-11.png deleted file mode 100644 index fdea99d..0000000 Binary files a/docs/distributed-system/img/mq-11.png and /dev/null differ diff --git a/docs/distributed-system/img/mq-2.png b/docs/distributed-system/img/mq-2.png deleted file mode 100644 index 1307bf0..0000000 Binary files a/docs/distributed-system/img/mq-2.png and /dev/null differ diff --git a/docs/distributed-system/img/mq-3.png b/docs/distributed-system/img/mq-3.png deleted file mode 100644 index 730a4d2..0000000 Binary files a/docs/distributed-system/img/mq-3.png and /dev/null differ diff --git a/docs/distributed-system/img/mq-4.png b/docs/distributed-system/img/mq-4.png deleted file mode 100644 index ec8d19b..0000000 Binary files a/docs/distributed-system/img/mq-4.png and /dev/null differ diff --git a/docs/distributed-system/img/mq-5.png b/docs/distributed-system/img/mq-5.png deleted file mode 100644 index c1fb950..0000000 Binary files a/docs/distributed-system/img/mq-5.png and /dev/null differ diff --git a/docs/distributed-system/img/mq-6.png b/docs/distributed-system/img/mq-6.png deleted file mode 100644 index c91224f..0000000 Binary files a/docs/distributed-system/img/mq-6.png and /dev/null differ diff --git a/docs/distributed-system/img/mq-7.png b/docs/distributed-system/img/mq-7.png deleted file mode 100644 index 232f846..0000000 Binary files a/docs/distributed-system/img/mq-7.png and /dev/null differ diff --git a/docs/distributed-system/img/mq-8.png b/docs/distributed-system/img/mq-8.png deleted file mode 100644 index 7e71479..0000000 Binary files a/docs/distributed-system/img/mq-8.png and /dev/null differ diff --git a/docs/distributed-system/img/mq-9.png b/docs/distributed-system/img/mq-9.png deleted file mode 100644 index 477edb1..0000000 Binary files a/docs/distributed-system/img/mq-9.png and /dev/null differ diff --git a/docs/high-availability/img/mq-1.png b/docs/high-availability/img/mq-1.png deleted file mode 100644 index a94f01e..0000000 Binary files a/docs/high-availability/img/mq-1.png and /dev/null differ diff --git a/docs/high-availability/img/mq-10.png b/docs/high-availability/img/mq-10.png deleted file mode 100644 index 25aabf0..0000000 Binary files a/docs/high-availability/img/mq-10.png and /dev/null differ diff --git a/docs/high-availability/img/mq-11.png b/docs/high-availability/img/mq-11.png deleted file mode 100644 index fdea99d..0000000 Binary files a/docs/high-availability/img/mq-11.png and /dev/null differ diff --git a/docs/high-availability/img/mq-2.png b/docs/high-availability/img/mq-2.png deleted file mode 100644 index 1307bf0..0000000 Binary files a/docs/high-availability/img/mq-2.png and /dev/null differ diff --git a/docs/high-availability/img/mq-3.png b/docs/high-availability/img/mq-3.png deleted file mode 100644 index 730a4d2..0000000 Binary files a/docs/high-availability/img/mq-3.png and /dev/null differ diff --git a/docs/high-availability/img/mq-4.png b/docs/high-availability/img/mq-4.png deleted file mode 100644 index ec8d19b..0000000 Binary files a/docs/high-availability/img/mq-4.png and /dev/null differ diff --git a/docs/high-availability/img/mq-5.png b/docs/high-availability/img/mq-5.png deleted file mode 100644 index c1fb950..0000000 Binary files a/docs/high-availability/img/mq-5.png and /dev/null differ diff --git a/docs/high-availability/img/mq-6.png b/docs/high-availability/img/mq-6.png deleted file mode 100644 index c91224f..0000000 Binary files a/docs/high-availability/img/mq-6.png and /dev/null differ diff --git a/docs/high-availability/img/mq-7.png b/docs/high-availability/img/mq-7.png deleted file mode 100644 index 232f846..0000000 Binary files a/docs/high-availability/img/mq-7.png and /dev/null differ diff --git a/docs/high-availability/img/mq-8.png b/docs/high-availability/img/mq-8.png deleted file mode 100644 index 7e71479..0000000 Binary files a/docs/high-availability/img/mq-8.png and /dev/null differ diff --git a/docs/high-availability/img/mq-9.png b/docs/high-availability/img/mq-9.png deleted file mode 100644 index 477edb1..0000000 Binary files a/docs/high-availability/img/mq-9.png and /dev/null differ diff --git a/docs/high-concurrency/how-to-ensure-high-availability-of-message-queues.md b/docs/high-concurrency/how-to-ensure-high-availability-of-message-queues.md index 80de672..9126502 100644 --- a/docs/high-concurrency/how-to-ensure-high-availability-of-message-queues.md +++ b/docs/high-concurrency/how-to-ensure-high-availability-of-message-queues.md @@ -31,14 +31,14 @@ RabbitMQ 有三种模式：单机模式、普通集群模式、镜像集群模 所以这个事儿就比较尴尬了，这就**没有什么所谓的高可用性**，**这方案主要是提高吞吐量的**，就是说让集群中多个节点来服务某个 queue 的读写操作。 #### 镜像集群模式（高可用性） -这种模式，才是所谓的 RabbitMQ 的高可用模式，跟普通集群模式不一样的是，你创建的 queue，无论元数据还是 queue 里的消息都会**存在于多个实例上**，然后每次你写消息到 queue 的时候，都会自动把**消息同步**到多个实例的 queue 上。 +这种模式，才是所谓的 RabbitMQ 的高可用模式。跟普通集群模式不一样的是，在镜像集群模式下，你创建的 queue，无论元数据还是 queue 里的消息都会**存在于多个实例上**，就是说，每个 RabbitMQ 节点都有这个 queue 的一个**完整镜像**，包含 queue 的全部数据的意思。然后每次你写消息到 queue 的时候，都会自动把**消息同步**到多个实例的 queue 上。 ![mq-8](/img/mq-8.png) -这样的话，好处在于，你任何一个机器宕机了，没事儿，别的机器都可以用。坏处在于，第一，这个性能开销也太大了吧，消息同步所有机器，导致网络带宽压力和消耗很重！第二，这么玩儿，就**没有扩展性可言**了，如果某个 queue 负载很重，你加机器，新增的机器也包含了这个 queue 的所有数据，并没有办法线性扩展你的 queue。 - 那么**如何开启这个镜像集群模式**呢？其实很简单，RabbitMQ 有很好的管理控制台，就是在后台新增一个策略，这个策略是**镜像集群模式的策略**，指定的时候是可以要求数据同步到所有节点的，也可以要求同步到指定数量的节点，再次创建 queue 的时候，应用这个策略，就会自动将数据同步到其他的节点上去了。 +这样的话，好处在于，你任何一个机器宕机了，没事儿，其它机器（节点）还包含了这个 queue 的完整数据，别的 consumer 都可以到其它节点上去消费数据。坏处在于，第一，这个性能开销也太大了吧，消息需要同步到所有机器上，导致网络带宽压力和消耗很重！第二，这么玩儿，不是分布式的，就**没有扩展性可言**了，如果某个 queue 负载很重，你加机器，新增的机器也包含了这个 queue 的所有数据，并**没有办法线性扩展**你的 queue。你想，如果这个 queue 的数据量很大，大到这个机器上的容量无法容纳了，此时该怎么办呢？ + ### Kafka 的高可用性 Kafka 一个最基本的架构认识：由多个 broker 组成，每个 broker 是一个节点；你创建一个 topic，这个 topic 可以划分为多个 partition，每个 partition 可以存在于不同的 broker 上，每个 partition 就放一部分数据。 diff --git a/docs/high-concurrency/img/mq-7.png b/docs/high-concurrency/img/mq-7.png index 232f846..5ef97cb 100644 Binary files a/docs/high-concurrency/img/mq-7.png and b/docs/high-concurrency/img/mq-7.png differ diff --git a/docs/high-concurrency/img/mq-8.png b/docs/high-concurrency/img/mq-8.png index 7e71479..e422bd5 100644 Binary files a/docs/high-concurrency/img/mq-8.png and b/docs/high-concurrency/img/mq-8.png differ diff --git a/docs/high-concurrency/mq-interview.md b/docs/high-concurrency/mq-interview.md index 1c48c88..6e30484 100644 --- a/docs/high-concurrency/mq-interview.md +++ b/docs/high-concurrency/mq-interview.md @@ -12,7 +12,7 @@ **面试官**：那你说一下你们在项目里是怎么用消息队列的？ -**候选人**：巴拉巴拉，“我们啥啥系统发送个啥啥消息到队列，别的系统来消费啥啥的。比如我们有个订单系统，订单系统会每次下一个新的订单的时候，就会发送一条消息到`ActiveMQ`里面去，后台有个库存系统负责获取消息然后更新库存。” +**候选人**：巴拉巴拉，“我们啥啥系统发送个啥啥消息到队列，别的系统来消费啥啥的。比如我们有个订单系统，订单系统每次下一个新的订单的时候，就会发送一条消息到 `ActiveMQ` 里面去，后台有个库存系统负责获取消息然后更新库存。” （部分同学在这里会进入一个误区，就是你仅仅就是知道以及回答你们是怎么用这个消息队列的，用这个消息队列来干了个什么事情？） diff --git a/img/mq-7.png b/img/mq-7.png index 232f846..5ef97cb 100644 Binary files a/img/mq-7.png and b/img/mq-7.png differ diff --git a/img/mq-8.png b/img/mq-8.png index 7e71479..e422bd5 100644 Binary files a/img/mq-8.png and b/img/mq-8.png differ