<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Mi&amp;Bee Blog</title><link>/en/tags/architecture/</link><description>Recent content in Architecture on Mi&amp;Bee Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>蓝宝石的傻话</managingEditor><lastBuildDate>Mon, 20 Jun 2022 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/architecture/rss.xml" rel="self" type="application/rss+xml"/><item><title>Eyes On You: The 2022 Productization Journey of a Multi-Cloud Heterogeneous Monitoring Platform</title><link>/en/posts/telemetry/eyeonyou/</link><pubDate>Mon, 20 Jun 2022 00:00:00 +0000</pubDate><guid>/en/posts/telemetry/eyeonyou/</guid><description>&lt;p&gt;In the context of multi-cloud deployment, global networking, and exponential growth in service scale within internet businesses, monitoring platforms have long surpassed the basic &amp;ldquo;metric collection + alert notification&amp;rdquo; positioning, becoming the core infrastructure for ensuring end-to-end stability. This article, based on the real evolution of a large-scale internet enterprise monitoring platform, dissects the complete planning and implementation approach for upgrading the monitoring platform from &lt;strong&gt;large-scale coverage&lt;/strong&gt; to &lt;strong&gt;productization, usability, and intelligence&lt;/strong&gt; in 2022.&lt;/p&gt;</description></item><item><title>From Bottleneck Breakthrough to Platform Governance — The Full Evolution of an Internet Company's Monitoring Platform Architecture</title><link>/en/posts/architecture/monitor-system-architecture/</link><pubDate>Mon, 10 Jan 2022 00:00:00 +0000</pubDate><guid>/en/posts/architecture/monitor-system-architecture/</guid><description>&lt;p&gt;In the context of rapid internet business expansion, multi-cloud deployment, and exponential asset growth, the monitoring platform is a critical infrastructure for ensuring service stability. This article provides a complete review of &lt;strong&gt;a major internet company&amp;rsquo;s monitoring platform evolution from 2019 to 2021&lt;/strong&gt; — from solving legacy monitoring performance bottlenecks, to implementing cross-cloud distributed monitoring, to cloud-native platform governance — presenting the full transformation of the monitoring system from &lt;strong&gt;0 to 1 build → large-scale expansion → platform governance&lt;/strong&gt;.&lt;/p&gt;</description></item><item><title>Hybrid Cloud Cross-Region Monitoring System Governance: Autonomous + Unified Dual-Core Architecture Practice</title><link>/en/posts/architecture/monitor-cloud-architecture/</link><pubDate>Mon, 10 Jan 2022 00:00:00 +0000</pubDate><guid>/en/posts/architecture/monitor-cloud-architecture/</guid><description>&lt;p&gt;In the context of global business expansion and large-scale hybrid cloud deployment, &lt;strong&gt;cross-IDC, cross-border, multi-cloud heterogeneous&lt;/strong&gt; monitoring governance has become a core challenge for stability assurance. Traditional monitoring solutions either rely on expensive dedicated line upgrades that intrude on business architecture, or cannot balance node autonomy with global unification. Meanwhile, as a non-revenue infrastructure, the monitoring system must strictly control resource usage without allowing capability degradation.&lt;/p&gt;
&lt;p&gt;This article breaks down a practical &lt;strong&gt;cross-region monitoring system governance solution&lt;/strong&gt; from a real internet company, explaining how to achieve &lt;strong&gt;elastic scaling, cross-border coverage, node autonomy, and data unification&lt;/strong&gt; for the monitoring system without modifying business architecture or incurring business cross-domain costs.&lt;/p&gt;</description></item><item><title>Black-box Probing Monitoring System Architecture Design and Practice for Internet Companies</title><link>/en/posts/architecture/blackbox-system-architecture/</link><pubDate>Tue, 31 Aug 2021 00:00:00 +0000</pubDate><guid>/en/posts/architecture/blackbox-system-architecture/</guid><description>&lt;p&gt;In the full-link monitoring system of internet services, &lt;strong&gt;white-box monitoring&lt;/strong&gt; focuses on proactively uncovering potential issues and predicting risks, while &lt;strong&gt;black-box monitoring&lt;/strong&gt; is fault-oriented, rapidly detecting problems that have already occurred online. The two work together to form a complete monitoring闭环. Most internet companies have long had a monitoring blind spot for &lt;strong&gt;public network services and the user-side last mile&lt;/strong&gt;. User-side faults often only trigger investigation after users report issues. The black-box probing monitoring system was designed precisely to solve this industry pain point.&lt;/p&gt;</description></item><item><title>Eyes On You: From SRE Principles to Prometheus Monitoring System Implementation</title><link>/en/posts/telemetry/prometheus-first/</link><pubDate>Sat, 20 Jun 2020 00:00:00 +0000</pubDate><guid>/en/posts/telemetry/prometheus-first/</guid><description>&lt;p&gt;In the context of distributed internet services, high concurrency, and multi-cloud deployment, &lt;strong&gt;SRE (Site Reliability Engineering)&lt;/strong&gt; has become a core role in ensuring service availability, and the &lt;strong&gt;monitoring system&lt;/strong&gt; serves as SRE&amp;rsquo;s &amp;ldquo;eyes.&amp;rdquo; This article starts from SRE core principles, deconstructs the pain points of modern monitoring systems, technology stack selection, Prometheus core principles, and alerting best practices, presenting a practical enterprise-grade monitoring system construction methodology.&lt;/p&gt;
&lt;h2 id="sre-core-principles-stability-is-the-1-metric"&gt;SRE Core Principles: Stability is the #1 Metric&lt;/h2&gt;
&lt;p&gt;SRE&amp;rsquo;s core is &lt;strong&gt;ensuring continuous service stability through engineering practices&lt;/strong&gt;, focusing on capacity planning, cluster maintenance, fault tolerance, load balancing, and monitoring system construction. There are only 3 core measurement metrics:&lt;/p&gt;</description></item><item><title>Large Enterprise Email System Architecture Design and Full Mail Flow Analysis</title><link>/en/posts/architecture/mail-system-architecture/</link><pubDate>Wed, 10 Jun 2020 00:00:00 +0000</pubDate><guid>/en/posts/architecture/mail-system-architecture/</guid><description>&lt;p&gt;As enterprise digitalization scales up, large organizations demand extreme capabilities from email systems: &lt;strong&gt;independent deployment, high availability, global interoperability, security protection, and load balancing&lt;/strong&gt;. This article breaks down the practical architecture of a dedicated large enterprise email system, covering overall design, physical/logical deployment, core service systems, and the full send/receive mail flow, providing a reference technical solution for enterprise-level email architecture implementation.&lt;/p&gt;
&lt;h2 id="i-overall-system-architecture-design"&gt;I. Overall System Architecture Design&lt;/h2&gt;
&lt;p&gt;Large enterprise email systems adopt a layered architecture of &lt;strong&gt;&amp;ldquo;frontend gateway layer + load balancing layer + core service layer + backend independent mail system&amp;rdquo;&lt;/strong&gt;, balancing security isolation, traffic scheduling, and business independence. The overall architecture is as follows:&lt;/p&gt;</description></item><item><title>Overseas Email Delivery Acceleration Architecture — Smart Delivery Network in Practice</title><link>/en/archives/07-sdn-oversea/</link><pubDate>Tue, 16 Jan 2018 00:00:00 +0000</pubDate><guid>/en/archives/07-sdn-oversea/</guid><description>&lt;h2 id="introduction-challenges-of-overseas-email-delivery"&gt;Introduction: Challenges of Overseas Email Delivery&lt;/h2&gt;
&lt;p&gt;In globalized business scenarios, email delivery faces numerous challenges. Overseas email delivery must not only overcome network latency issues but also navigate complex geopolitical network environments. Traditional direct overseas delivery methods often encounter connection timeouts, firewall blocking, and high delivery latency. At the same time, interoperability between domestic email systems and overseas networks also presents technical challenges.&lt;/p&gt;
&lt;p&gt;To address these issues, we designed and implemented a Smart Delivery Network (SDN) architecture that effectively improves the efficiency and reliability of overseas email delivery through multi-level proxying, intelligent routing, and load balancing mechanisms.&lt;/p&gt;</description></item><item><title>Enterprise Mail System Architecture Design and Mail Flow Analysis</title><link>/en/archives/03-mail-system-design/</link><pubDate>Fri, 24 Feb 2017 00:00:00 +0000</pubDate><guid>/en/archives/03-mail-system-design/</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;In the digital era, email serves as a core communication tool for both internal and external enterprise interactions. Its architecture design directly impacts the stability, security, and performance of mail services. This article explores the three-tier architecture design of enterprise mail systems, provides a detailed analysis of the complete mail receiving and sending processes, and helps readers gain a comprehensive understanding of the technical implementation of modern mail systems.&lt;/p&gt;</description></item></channel></rss>