0基础成消息中间件高手

<div id="content_views" class="htmledit_views">
                    <h2><a name="t0"></a>一、第十五课&nbsp; 消息中间件的作用</h2>
<p>异步化提升性能、解耦、流量削峰</p>
<h2><a name="t1"></a>二、第十七课&nbsp; Kfaka、RabbitMQ、RocketMQ的比较&nbsp;</h2>
<p><img alt="" src="https://img-blog.csdnimg.cn/20210223151852800.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L2NvbHNwYW5wcmluY2U=,size_16,color_FFFFFF,t_70" width="853" height="500"></p>
<p>&nbsp;<img alt="" src="https://img-blog.csdnimg.cn/20210223152004286.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L2NvbHNwYW5wcmluY2U=,size_16,color_FFFFFF,t_70" width="845" height="486"></p>
<p><img alt="" src="https://img-blog.csdnimg.cn/20210223151935487.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L2NvbHNwYW5wcmluY2U=,size_16,color_FFFFFF,t_70" width="856" height="431"></p>
<h2><a name="t2"></a>三、第十九课&nbsp; RocketMQ基本架构图&nbsp;</h2>
<p style="text-align:center;"><img alt="" src="https://img-blog.csdnimg.cn/2021022315044672.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L2NvbHNwYW5wcmluY2U=,size_16,color_FFFFFF,t_70"></p>
<h2><a name="t3"></a>四、第二十一课&nbsp; NameServer</h2>
<div>
 &nbsp;
</div>
<p>1、每个Broker启动都向所有的NameServer注册</p>
<p>2、RocketMQ的生产者和消费者会主动去NameServer拉取Broker信息</p>
<h2><a name="t4"></a>五、第二十三课&nbsp; Broker的主从架构</h2>
<div>
 &nbsp;
</div>
<p>1、RocketMQ的Master-Slave模式是通过Pull模式拉取消息的，Slave Broker发送请求到Master Broker拉取消息</p>
<p>2、消费者拉取数据会先发到Master Broker上，但不一定会从Master Broker上获取，Master Broker会根据自身负载以及Slave Broker的同步情况，来决定从哪台机器拉取消息</p>
<h2><a name="t5"></a>六、第二十五课&nbsp; 设计一套高可用的RocketMQ部署架构</h2>
<p style="text-align:center;"><img alt="" src="https://img-blog.csdnimg.cn/20210209102933939.png?x-oss-process=image/watermark,type_ZmFuZ3poZW5naGVpdGk,shadow_10,text_aHR0cHM6Ly9ibG9nLmNzZG4ubmV0L2NvbHNwYW5wcmluY2U=,size_16,color_FFFFFF,t_70"></p>
                </div>