How do their APIs compare?

These two projects are fundamentally different in nature, so "APIs" means something quite different in each — jcsprout barely has one in the conventional sense, while datax-web has a proper web/REST API layer.

crossoverjie/jcsprout

This is a Java learning repository — a collection of standalone demos/examples covering concurrency, collections, JVM, algorithms, design patterns, etc. It's not a library or service exposing a consumable API. What you see instead are:

• Runnable example classes with main methods, e.g. [src/main/java/com/crossoverjie/concurrent/StopThread.java:L12-L37], which demonstrates thread interruption.
• Small illustrative class hierarchies for teaching patterns, like the callback pattern in [src/main/java/com/crossoverjie/guava/callback/Caller.java:L13-L80] (a Caller with a Notifier/CallBackListener collaborators), or the chain-of-responsibility pattern in [src/main/java/com/crossoverjie/design/pattern/chainofresponsibility/impl/TypoProcess.java:L12-L18].
• Benchmark harnesses using JMH annotations, e.g. [src/main/java/com/crossoverjie/basic/CollectionsTest.java:L1-L22].

There's no formal public "API" contract to consume — the "interface" is really just class/method design used to illustrate a concept.

weiye-jing/datax-web

This is an actual web application (a scheduling/admin UI for DataX ETL jobs), and it exposes real REST controller APIs built with Spring MVC, documented via Swagger:

• Swagger/OpenAPI setup: [datax-admin/src/main/java/com/wugui/datax/admin/config/SwaggerConfig.java:L24-L40] configures a Docket scanning the com.wugui.datax.admin.controller package, so all controllers there are auto-documented.
• REST controllers like JobRegistryController in [datax-admin/src/main/java/com/wugui/datax/admin/controller/JobRegistryController.java:L27-L91] expose paginated, filterable endpoints (e.g. selectAll() annotated with @GetMapping and Swagger @ApiImplicitParams for current, size, ascs, descs), returning a generic R<IPage<JobRegistry>> wrapper.
• Shared query-building helper in BaseForm [datax-admin/src/main/java/com/wugui/datax/admin/controller/BaseForm.java:L1-L26, L227-L253], which converts incoming request params into MyBatis-Plus QueryWrapper sort/filter conditions — a common pattern reused by controllers like JobRegistryController.
• Internal enums/model types used across the API surface, e.g. TriggerTypeEnum [datax-admin/src/main/java/com/wugui/datax/admin/core/trigger/TriggerTypeEnum.java:L10-L27] which models how a job trigger occurred (manual, cron, retry, parent, API).

So in short:

• jcsprout has no consumable API surface — it's educational sample code, and per the RepoPilot verdict it's flagged WAIT — Stale, last commit 2 years ago, reinforcing that it isn't maintained as a library/service.
• datax-web has a genuine layered API: Swagger-documented Spring REST controllers, generic response/pagination wrappers, and reusable query-building utilities — architecture typical of an admin backend service.

If you want, I can dig deeper into datax-web's job-trigger or executor-routing APIs (e.g. the consistent-hash routing strategy at [datax-admin/src/main/java/com/wugui/datax/admin/core/route/strategy/ExecutorRouteConsistentHash.java:L1-L19]) for a more detailed API walkthrough.

FOLLOW_UPS:

• What does ExecutorRouteConsistentHash actually implement?
• How does datax-web handle job pagination and filtering?
• What Java concurrency examples exist in jcsprout?