Why PowerJob Beats xxl-job: A More Powerful Distributed Scheduling Framework

Overview

PowerJob is a third‑generation distributed task scheduling and computation framework. It supports CRON, API, fixed‑frequency and fixed‑delay strategies and provides a visual workflow engine for defining DAG‑style task dependencies.

Why PowerJob

First‑generation Quartz lacks a web UI, works only via API and runs on a single node. Second‑generation xxl‑job improves on Quartz but still has three major drawbacks:

Database support limited to MySQL; other databases require code changes.

Distributed compute limited to static sharding.

No workflow support, preventing DAG‑based task orchestration.

PowerJob was created to address these limitations.

Key Features

Web UI for task CRUD, status monitoring and log viewing.

Four timing strategies: CRON, fixed‑frequency, fixed‑delay and API.

Four execution modes: single‑machine, broadcast, Map and MapReduce, enabling cluster‑wide computation with minimal code.

DAG workflow support with visual task orchestration and upstream‑downstream data passing.

Broad executor compatibility: Spring Bean, built‑in or external Java classes, Shell, Python, etc.

Online log display reduces debugging cost.

Lightweight dependencies – only relational databases (MySQL, PostgreSQL, Oracle, SQL Server) are required; all Spring Data JPA‑supported databases work.

Lock‑free scheduling design allows horizontal scaling by adding scheduler servers for high availability and performance.

Configurable retry policies provide fault‑tolerance for failed tasks.

Product Comparison

Applicable Scenarios

Periodic jobs such as nightly data sync or report generation.

Broadcast tasks that must run on every machine, e.g., cluster‑wide log cleanup.

Distributed processing tasks, like bulk data updates that benefit from Map/MapReduce parallelism.

Overall Architecture

Related Links

Project repository: https://github.com/KFCFans/PowerJob

Official documentation: https://www.yuque.com/powerjob/guidence/intro

Online trial: https://www.yuque.com/powerjob/guidence/trial

Quick Start

PowerJob consists of a scheduler server (powerjob‑server) that provides the web UI and schedules tasks, and an executor (powerjob‑worker) that runs user code and offers distributed compute.

Initialize Project

Clone the repository:

git clone https://github.com/KFCFans/PowerJob.git

Import the project into an IDE. The source layout contains the scheduler server module and a samples module for custom processors.

Start Scheduler Server

Create a database named powerjob-daily.

Edit the configuration file to set spring.datasource.core.jdbc-url, spring.datasource.core.username, spring.datasource.core.password (or spring.data.mongodb.uri for MongoDB).

Launch the server via the main class com.github.kfcfans.powerjob.server.OhMyApplication and verify startup logs. Access http://127.0.0.1:7700/ to view the UI.

Register an application in the UI (e.g., oms-test) with a console password.

Write Sample Code

Enter the powerjob-worker-samples module, adjust connection settings, and implement a processor.

Modify the startup config class com.github.kfcfans.powerjob.samples.OhMySchedulerConfig to replace the placeholder AppName with the name registered in the console.

Create a processor class that extends the desired processor type; the example uses the single‑machine BasicProcessor.

Run the sample application via its main class com.github.kfcfans.powerjob.samples.SampleApplication and check the console for successful startup.

Configure and Run Tasks

With both server and sample worker running, open the web UI at http://127.0.0.1:7700/:

Enter the registered app name on the home page to access the management console.

Navigate to “Task Management → New Task” to create a job.

After creation, the task appears in the console; click “Run” to execute it immediately.

Use the “Task Example” sidebar to view execution status and live logs.

The basic tutorial ends here; additional features such as advanced workflows, MapReduce and container integration are documented in the official guide.