The Journey of Dubbogo: From Solo Development to a Thriving Open‑Source Community
This article chronicles how 于雨 transformed Dubbogo—from a one‑person Go implementation of the Dubbo RPC framework into a large, cloud‑native open‑source community—detailing technical challenges, community building, personal sacrifices, and future goals for sustainable growth.
于雨, a technical expert at Ant Group, started Dubbogo as a personal side project to create a Go version of the high‑performance Java RPC framework Dubbo. Initially maintained alone, he built the communication layer in two months and later opened the project to the public, committing to long‑term maintenance.
For over two years, 于雨 faced daunting technical hurdles—re‑implementing Dubbo’s extensive features in Go, handling missing libraries, and fixing numerous bugs—while also struggling to attract contributors and users. Despite skepticism from the community, he secured early adopters such as Tuyu Smart and gradually grew the contributor base.
As Dubbogo joined the Apache ecosystem in 2019, the community expanded to 60‑70 active contributors, with multiple sub‑projects (pixiu, arana) and over 350,000 lines of code. The project now aligns with Dubbo across all versions and integrates with cloud‑native platforms like Kubernetes, Spring Cloud, and gRPC.
Looking ahead, the roadmap emphasizes deeper cloud‑native adoption, lightweight design, improved usability, and broader interoperability with systems such as RocketMQ and MySQL. 于雨 stresses the importance of long‑term commitment, community cohesion, and a mindset that tolerates the solitude inherent in infrastructure‑level open‑source work.
Beyond technical achievements, the interview highlights personal insights: the spiritual satisfaction of open‑source contribution, the need for balanced time management, and the value of mentorship and community support in sustaining a healthy, long‑lasting project.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
