Interview with GIAC Microservices Lecturer Hu Zhongxiang on Weibo's Microservices Practices

From November 23‑24, the GIAC Global Internet Architecture Conference will be held in Shanghai, featuring experts from companies such as Microsoft, Tencent, Alibaba, Ant Financial, Huawei, iFlytek, Sina Weibo, JD.com, Qiniu, Meituan‑Dianping, Ele.me, and others.

In the lead‑up to the conference, High Availability Architecture interviewed GIAC microservices lecturer Hu Zhongxiang to discuss practical microservice implementation issues.

Hu Zhongxiang is a Weibo technology expert and author of the GeekTime column “Learning Microservices from Scratch”. He has been with Weibo since 2012, working on counter upgrades, major event support, and homepage feed architecture, accumulating extensive experience in high‑availability distributed services.

Q: As a Weibo “net‑celebrity” tech expert, how does that feel? Hu explains that the pressure is high because any service outage at Weibo becomes a widely shared meme, highlighting the platform’s critical role in delivering hot‑topic information.

Q: What advantages does a microservice architecture bring for handling sudden hot‑topic events? He describes Weibo’s dynamic decision system that automatically scales services based on pool redundancy, eliminating manual intervention. For newer business lines built in PHP, the system was adapted into a microservice solution called Weibo Mesh, enabling seamless integration across multiple services.

Q: What are the biggest challenges when adopting microservices? While many components (service framework, registry, monitoring, tracing, governance) are complex to build in‑house, Hu believes the toughest challenge is technology selection—deciding between custom development and open‑source solutions, and choosing appropriate frameworks such as Dubbo, Spring Cloud, gRPC, or Thrift.

Q: How should services be split? He advises against overly fine‑grained splitting. Weibo started by dividing a large monolithic web app into two, then gradually extracted several RPC services over two‑three years as the team grew, emphasizing a step‑by‑step approach.

Q: What changes are needed to migrate from other architectures to microservices? Hu notes that microservices combined with containerization and DevOps enable rapid iteration and faster development when the business scale is large.

Q: How do microservices relate to Cloud Native? Microservices focus on business organization, while Cloud Native concerns deployment models. When both are adopted, they complement each other, exemplified by Service Mesh solutions like Istio.

Q: What learning path do you recommend for quickly mastering microservices? Start with the basic principles and practice with an open‑source framework such as Dubbo, Motan, or Spring Cloud, ideally within a real project.

Q: What will you share at the GIAC microservices session? Hu will present Weibo’s frontline experience in service governance, including a custom static registry, backup‑request pattern, best‑fit load‑balancing algorithm, cross‑language governance practices, and the unified microservice governance platform.

Q: Any final words for GIAC? He hopes his talk will benefit attendees and foster deeper exchanges with peers.

The microservices track at this GIAC conference includes a range of exciting topics (see image).