Discofork
Repository brief

apache/dubbo

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T16:04:28.835Z
1mo ago

apache/dubbo

Apache Dubbo is a large, actively maintained JVM RPC and microservice framework with strong ecosystem breadth and a very mature fork/star footprint. It appears best suited for teams evaluating a production-grade service framework rather than a small niche library.

GitHub
Loading tags...
Stars41,685
Forks26,522
Default branch3.3
Last pushed2026-03-30T07:11:05Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if you specifically need its legacy Dubbo extensions. For new work, upstream Apache Dubbo is the safer default because this fork is stale and materially behind.

Choose this fork only if you want a historical, source-reading-oriented Dubbo variant or need legacy compatibility. For new production work, upstream Apache Dubbo is the safer choice.

Prefer this fork only if you specifically need its older 2.7-era fixes and can accept major divergence from modern upstream Dubbo. For new adopters or teams wanting current platform breadth, upstream is the safer default.

Adopt this fork only if you specifically need its older custom protocol/codegen behavior or are maintaining an existing legacy branch. For new production work, upstream Apache Dubbo is the safer choice because this fork is stale and materially diverged.

Prefer the upstream project for any active service framework work. Choose this fork only if you need its historical async experiment, legacy compatibility, or benchmark-specific changes and accept that it is materially outdated and divergent.

Choose this fork only if you need the old Dubbo codebase or a legacy-compatibility research baseline. If you want a production framework with active maintenance, modern protocols, and current ecosystem support, upstream Apache Dubbo is the better choice.

Choose this fork only if you need its custom packaging/runtime behavior and can own the maintenance burden. If you want current Dubbo features, upstream alignment, and lower integration risk, upstream Apache Dubbo is the safer default.

Choose this fork only if you specifically need its legacy, heavily customized 2021-era behavior, especially around generated Thrift/codegen workflows. For most adopters, upstream Apache Dubbo is the better default because this fork is stale, significantly diverged, and likely missing years of upstream fixes and compatibility work.

Choose this fork only if you need its specific legacy Nacos/Thrift/customization work. For most adopters, upstream Dubbo is the better choice because this fork is stale and substantially behind current maintenance.

Prefer this fork only if its MCP and protocol experiments are the point of adoption. If you want a current, broadly supported Dubbo platform, upstream is the safer choice because this fork is both significantly divergent and well behind.

apache/dubbo · Discofork