[{"data":1,"prerenderedAt":262},["ShallowReactive",2],{"blog-post-zh-nanomq-newsletter-202111":3},{"post":4,"translationPath":261},{"id":5,"title":6,"author":7,"body":8,"cover":245,"coverHeight":246,"coverWidth":247,"date":248,"description":249,"draft":250,"extension":251,"meta":252,"navigation":253,"path":254,"pinned":250,"seo":255,"sitemap":256,"stem":257,"tags":258,"__hash__":260},"blog_zh\u002Fzh\u002Fblog\u002Fnanomq-newsletter-202111.md","NanoMQ Newsletter 202111：为 NNG 增加 MQTT 支持",null,{"type":9,"value":10,"toc":226},"minimark",[11,28,33,43,47,62,70,73,76,85,88,93,96,100,103,114,123,126,130,133,136,147,150,153,156,159,215,218],[12,13,14,15,22,23,27],"p",{},"11 月 NanoMQ 团队主要致力于为 NNG 添加 ",[16,17,21],"a",{"href":18,"rel":19},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fmqtt-guide",[20],"nofollow","MQTT"," 支持，同时对 ",[16,24,26],{"href":25},"\u002Fzh","NanoMQ"," 进行了一些更新。",[29,30,32],"h2",{"id":31},"nanomq-更新","NanoMQ 更新",[34,35,36,40],"ul",{},[37,38,39],"li",{},"优化了配置文件的日志打印输出，会自动根据是否指定配置文件路径判断是否输出告警信息。",[37,41,42],{},"Bug 修复：当客户端批量订阅多个主题时，NanoMQ 无法按照正确的订阅 QoS 等级来转发消息。",[29,44,46],{"id":45},"nng-现已支持-mqtt","NNG 现已支持 MQTT",[12,48,49,50,55,56,61],{},"NanoMQ 是 EMQ 与 NNG 合作的开源项目。在 NanoMQ 的 GitHub 仓库内部有一个 NNG 的 sub-module，其为 NanoMQ 单独维护的 NNG 版本（",[16,51,54],{"href":52,"rel":53},"https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fnng\u002Ftree\u002Fmaster",[20],"GitHub 项目地址","）。目前其 master 分支是 NanoMQ 为 ",[16,57,60],{"href":58,"rel":59},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fthe-ultimate-guide-to-mqtt-broker-comparison",[20],"MQTT Broker"," 单独开发优化并独立维护的特殊版本，从中我们已经为 NNG 提交了若干有价值的 PR 和 Issue。但此分支与 nanomsg 的 SP 协议并不兼容。",[12,63,64,65,69],{},"本月我们主要致力于为 NNG 添加 ",[16,66,21],{"href":67,"rel":68},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fthe-easiest-guide-to-getting-started-with-mqtt",[20]," 3.1.1 协议支持，从而使 NanoMQ 与 NNG 的 SP 协议兼容，以便两个项目未来能更好地共同使用。这也与 NanoMQ 之前制定的 RoadMap 方向一致。",[12,71,72],{},"根据之前和 NNG 项目维护者 Garrett 在开源合作会议上共同制定的技术目标，NNG 未来会增加支持ZeroMQ 和MQTT 3.1.1\u002F5.0。经过一个月的努力，我们已经完成了 MQTT 3.1.1 协议的开发支持，并将其命名为 NanoSDK。NanoSDK 内部设计保留了 NNG 框架的编程风格，兼容 NNG 原有的 SP 协议。同时不影响其 HTTP\u002FWebsocket\u002FTLS 等功能的使用。",[12,74,75],{},"相较于其他 MQTT 3.1.1 SDK，NanoSDK 具有以下优势：",[77,78,80,84],"h3",{"id":79},"全异步-io-和良好的-smp-支持",[81,82,83],"strong",{},"全异步 I\u002FO 和良好的 SMP 支持","。",[12,86,87],{},"通过 NNG 的全异步 I\u002FO 实现 C 语言的 Actor 编程模型，可以很好的将负载均衡分配到多个 CPU 核心。",[77,89,91],{"id":90},"高度兼容性和移植性",[81,92,90],{},[12,94,95],{},"继承了 NNG 的兼容性和易于移植的特点，只依赖原生 POSIX 标准 API，对各种类 Linux 构建系统友好。方便移植到新硬件和操作系统平台。",[77,97,99],{"id":98},"支持多种-api-风格","支持多种 API 风格",[12,101,102],{},"NNG 框架的编程风格有较高的上手门槛，需要用户对其 AIO 和 Context 的使用有深入认识。所以我们也为习惯于使用 Paho 和 Mosquitto sdk 的用户准备了传统的回调注册机制。这样在降低编程难度的同时也能兼得 NNG 的优势。",[77,104,106,107,110,111],{"id":105},"高吞吐-低延时","高吞吐 ",[81,108,109],{},"&"," ",[81,112,113],{},"低延时",[12,115,116,117,122],{},"在 NanoMQ 的测试报告中已经体现出了其强大的高吞吐和低延时性能优势，与其一脉相承 Nano MQTT SDK 也一样在性能方面有出色表现。其占用资源性价比高，不同于传统 ",[16,118,121],{"href":119,"rel":120},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fmqtt-client-sdk",[20],"MQTT SDK"," 只有1-2个线程。NanoSDK 可以完全利用系统硬件资源，提供更高消费吞吐能力。",[12,124,125],{},"在大部分基于 EMQX 构建的物联网架构中，端侧和消费侧的处理性能不足导致消息积压一直是困扰开源开发者的难题。特别是对于 QoS 1\u002F2 消息而言，大部分 SDK 对于 QoS 1\u002F2 消息都是同步阻塞 Ack。而 NanoSDK 在保证了 QoS 消息顺序和消息重发机制的前提下，提供了异步 Ack 能力，大大提高了 QoS 1\u002F2 的吞吐消费能力。",[29,127,129],{"id":128},"附nanosdk-与-paho-c-mqtt-sdk-性能对比测试报告","附：NanoSDK 与 Paho C MQTT SDK 性能对比测试报告",[12,131,132],{},"我们选取当前较为广泛使用的 Paho C MQTT SDK 与 NanoSDK 进行了性能对比测试。",[77,134,135],{"id":135},"测试环境",[34,137,138,141,144],{},[37,139,140],{},"Quad Core model: 11th Gen Intel Core i7-1165G7",[37,142,143],{},"16G memory",[37,145,146],{},"500K PUBLISH message with 2 bytes payload",[77,148,149],{"id":149},"测试场景逻辑",[12,151,152],{},"建立一个客户端连接 EMQX 完成收发 50000 条 QoS 0\u002F1\u002F2 消息（两者都只统计总共读 Socket 占用时间来计算消息速率）。为了贴近大部分真实业务场景，我们用 emqtt_bench 工具发送2字节的消息给此客户端，客户端每次收到一条消息都将回复14字节的 Publish 消息，客户端每次处理一发一收的消息。两个与场景除了使用的 SDK 不同外，其余条件保持一致。",[77,154,155],{"id":155},"测试结果",[12,157,158],{},"具体时间数字可能每次测试有细微不同。",[160,161,162,179],"table",{},[163,164,165],"thead",{},[166,167,168,173,176],"tr",{},[169,170,172],"th",{"align":171},"left","Qos",[169,174,175],{"align":171},"NanoSDK（NNG）",[169,177,178],{"align":171},"Paho C MQTT",[180,181,182,194,204],"tbody",{},[166,183,184,188,191],{},[185,186,187],"td",{"align":171},"0",[185,189,190],{"align":171},"2946 msg\u002Fs",[185,192,193],{"align":171},"2944 msg\u002Fs",[166,195,196,199,201],{},[185,197,198],{"align":171},"1",[185,200,193],{"align":171},[185,202,203],{"align":171},"610 msg\u002Fs",[166,205,206,209,212],{},[185,207,208],{"align":171},"2",[185,210,211],{"align":171},"2919 msg\u002Fs",[185,213,214],{"align":171},"585 msg\u002Fs",[12,216,217],{},"可见在多核平台中，单个客户端情况下，NanoSDK 在 QoS 1\u002F2 场景有着巨大优势。同时由于 NanoSDK 基于 NNG 用 C 语言实现了 MQTT 的类 Actor 编程模型，全异步 I\u002FO 实现可以很好地将负载均衡分配到多个 CPU 核心。开发者可以按照我们的 Context 例程启动多个 MQTT 连接来达到 QoS 0 的更高消费能力，而不用苦恼于多线程并发开发。",[12,219,220,221,225],{},"NanoMQ 团队计划于 12 月与 NNG 项目维护者 Garrett 举行开源开发会议，讨论如何双方项目的合并事宜。欢迎大家试用 NanoMQ Fork 的 NNG 仓库内的 nng-mqtt 分支",[16,222,223],{"href":223,"rel":224},"https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fnng\u002Ftree\u002Fnng-mqtt",[20],"，抢先体验。",{"title":227,"searchDepth":228,"depth":228,"links":229},"",2,[230,231,240],{"id":31,"depth":228,"text":32},{"id":45,"depth":228,"text":46,"children":232},[233,236,237,238],{"id":79,"depth":234,"text":235},3,"全异步 I\u002FO 和良好的 SMP 支持。",{"id":90,"depth":234,"text":90},{"id":98,"depth":234,"text":99},{"id":105,"depth":234,"text":239},"高吞吐 & 低延时",{"id":128,"depth":228,"text":129,"children":241},[242,243,244],{"id":135,"depth":234,"text":135},{"id":149,"depth":234,"text":149},{"id":155,"depth":234,"text":155},"\u002Fimages\u002Fblog\u002Fzh\u002Fnanomq-newsletter-202111\u002Fcover.webp",684,1520,"2021-12-01","11 月 NanoMQ 团队主要致力于为 NNG 添加 MQTT 支持，同时对 NanoMQ 进行了一些更新。",false,"md",{},true,"\u002Fzh\u002Fblog\u002Fnanomq-newsletter-202111",{"title":6,"description":249},{"loc":254,"lastmod":248},"zh\u002Fblog\u002Fnanomq-newsletter-202111",[259],"NanoMQ Newsletter","HchFZnPgT7yoZWsT4LvirADH9GvvIs1Vw87p3Nqqogs","\u002Fblog\u002Fnanomq-newsletter-202111",1794542897606]