https://blog.mickeyzzc.tech/en/tags/distributed/Recent content in Distributed on Mi&Bee BlogHugo -- gohugo.ioen蓝宝石的傻话Mon, 13 Jul 2026 00:00:00 +0000https://blog.mickeyzzc.tech/en/posts/mibee-oss/mibeesteward-v0.2-promo/Mon, 13 Jul 2026 00:00:00 +0000https://blog.mickeyzzc.tech/en/posts/mibee-oss/mibeesteward-v0.2-promo/<p>When v0.1.0 <a href="https://blog.mickeyzzc.tech/en/posts/mibee-oss/mibeesteward-introduction/">shipped</a>, I wrote that it answers three questions: what devices are on the network, what they are, and how they relate. Honestly, v0.1.0 only answered the first half well — and only for the one LAN the center sat on.</p> <p>The real-world layout is messier: one subnet in the office, one in the server room, another at home for test machines. The center lives in the office and literally cannot see the cameras in the server room. Getting it to scan the server room means crossing subnets — either opening up SNMP routing or just moving the center over there. Neither is elegant.</p>https://blog.mickeyzzc.tech/en/posts/mibee-oss/mibeesteward-v0.2-tech/Mon, 13 Jul 2026 00:00:00 +0000https://blog.mickeyzzc.tech/en/posts/mibee-oss/mibeesteward-v0.2-tech/<p>The <a href="https://blog.mickeyzzc.tech/en/posts/mibee-oss/mibeesteward-v0.2-promo/">previous post</a> covered what v0.2.0 ships. This one covers why it&rsquo;s designed that way — distributed consistency is the heaviest part of this release, and several seemingly casual decisions have specific trade-offs behind them.</p> <p>The problem is clear: the center can only see its own LAN, but users have several. Dropping a center into every subnet isn&rsquo;t realistic, so enter <code>mibee-agent</code> — a binary that only &ldquo;scans local + reports to center.&rdquo; But the moment an agent exists, it drags along a whole string of protocol questions: how to report, how to reconcile, how to detect offline, how not to overwhelm the center&rsquo;s writes. Let&rsquo;s take them one at a time.</p>