Discofork
Repository brief

xuxueli/xxl-job

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-30T19:52:53.775Z
1mo ago

xuxueli/xxl-job

XXL-JOB is a mature, actively maintained distributed task scheduling framework. The repository is large and widely forked/starred, with recent commits on 2026-03-29 focused on documentation, scheduler fixes, database index/performance work, and query/log improvements. For fork evaluation, it looks most interesting if you want a Java/JVM-based scheduler platform with an admin console, executor samples, and a long feature list already present upstream.

GitHub
Loading tags...
Stars30,001
Forks11,453
Default branchmaster
Last pushed2026-03-29T11:05:17Z
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 if you want XXL-JOB adapted for an R3 deployment and are comfortable trading some upstream freshness for integration-specific changes. Stay with upstream if you want the broadest compatibility and the latest scheduler fixes without fork-specific assumptions.

Prefer upstream unless you specifically need this fork’s older PostgreSQL/TiDB-oriented changes or are already locked to its baseline. For new adoption, the age and drift make it a maintenance risk rather than a strong starting point.

Adopt this only if you specifically need a frozen, older admin snapshot. For most users, upstream is the better choice because this fork adds nothing and is far behind on fixes and performance work.

Prefer upstream unless you specifically need the Oracle support or older fork-specific behavior; this fork is too stale for most new adopters and carries a high rebase/maintenance burden.

Prefer upstream unless you specifically need this exact historical snapshot. This fork adds no visible capabilities and is materially behind on maintenance and performance fixes, so it is a poor default choice for new adopters.

Choose this fork only if you need the specific weekday scheduling correction and are comfortable living on an old, lightly maintained branch. For most adopters, upstream is the better base because this fork adds little beyond a small bugfix and is far behind current upstream work.

如果你要的是可定制的分片优先调度执行模型，这个 fork 有明确价值；如果你更看重持续维护、兼容性和上游完整功能，直接选 upstream 更稳妥。

Prefer this fork only if you need its legacy API/customization and are committed to maintaining an older codebase. For new adopters, upstream is the better default because this fork is stale and materially behind on features, fixes, and maintenance.

Prefer upstream unless custom request expiration is the exact requirement. This fork looks like a narrow historical customization, not a broader alternative distribution, and it is far too stale for most new deployments.

Choose this fork if your main constraint is database portability or you need batch admin workflows. Choose upstream if you want the freshest scheduler fixes and the lowest maintenance burden.