Master PowerJob: A Modern Java Distributed Task Scheduling Framework

Recently, a project adopted PowerJob for task scheduling, revealing its powerful features as a next‑generation distributed scheduling framework.

Introduction

Easy to use : Provides a front‑end web UI for visual management of tasks (CRUD), status monitoring, and log viewing.

Rich timing strategies : Supports CRON expressions, fixed frequency, fixed delay, and API‑triggered schedules.

Multiple execution modes : Single‑node, broadcast, Map, and MapReduce modes; Map/MapReduce enable cluster‑level distributed computation with minimal code.

Workflow support : Allows online configuration of task dependencies (DAG) with data passing and node types such as conditional and nested workflow nodes.

Broad executor support : Supports Spring Bean, built‑in/external Java classes, and via official dependencies can integrate Shell, Python, HTTP, SQL, etc.

Operations friendly : Real‑time log display in the console reduces debugging cost.

Lightweight dependencies : Requires only a relational database (MySQL/PostgreSQL/Oracle/SQLServer).

High availability & performance : Uses a lock‑free design; multiple servers can be deployed for horizontal scaling.

Failover & recovery : Automatic retry based on configured policies.

Compared with other scheduling frameworks, PowerJob’s lock‑free architecture offers stronger performance, as shown in the official product comparison.

Installation

PowerJob can be installed via a JAR package or Docker. Docker installation is straightforward; refer to the official documentation for details.

To run via JAR:

Download the source code from https://github.com/PowerJob/PowerJob and compile or obtain a release version.

Open the project in an IDE and locate powerjob-server (server source) and powerjob-worker-samples (Spring Boot sample).

Create a database, e.g.:

CREATE DATABASE IF NOT EXISTS `powerjob-daily` DEFAULT CHARSET utf8mb4;

Modify application-daily.properties under powerjob-server-starter to set the database connection and environment (daily, pre, product).

Run the main class PowerJobServerApplication locally; access http://localhost:7700 to see the login page.

Register an executor (application name must match the client configuration).

Log in with the executor name and password.

For server deployment, execute mvn install to install dependencies, then mvn package to build the JAR, and finally run it with java -jar.

Creating Scheduled Tasks

Create a Spring Boot project for the client and add the dependency:

<dependency>
    <groupId>tech.powerjob</groupId>
    <artifactId>powerjob-worker-spring-boot-starter</artifactId>
    <version>4.3.2</version>
</dependency>

Configure application.yml (or properties) with PowerJob worker settings, e.g.:

powerjob:
  worker:
    enabled: true
    enable-test-mode: false
    port: 27777
    app-name: powerjob-agent-test
    server-address: 127.0.0.1:7700
    protocol: http
    max-result-length: 4096
    max-lightweight-task-num: 1024
    max-heavy-task-num: 64

Add @EnableScheduling to the Spring Boot main class.

Implement a task processor by creating a bean that implements BasicProcessor, for example:

/**
 * Simple job implementation
 */
@Component
public class SimpleJobServer implements BasicProcessor {
    @Override
    public ProcessResult process(TaskContext taskContext) throws Exception {
        String jobParams = taskContext.getJobParams();
        System.out.println("参数: " + jobParams);
        System.out.println("定时任务执行");
        return new ProcessResult(true, "定时任务执行成功");
    }
}

Start the client project; the server UI will display the new machine instance.

In the server UI, create a new task, specifying the processor class name (e.g., com.example.powerjobdemo.job.SimpleJobServer).

After creation, the task appears in the task list and executes on the client, with logs visible both on the server UI and the client console.

Task Configuration Parameters Details

When creating a task, the UI presents several configuration sections:

Timing information : Choose the task type—API, CRON, fixed frequency, fixed delay, workflow, or daily fixed interval.

Lifecycle : Define the effective period for the task, useful for scheduling within a specific time window.

Execution configuration : Select execution mode (single, broadcast, Map, MapReduce) and understand their use cases.

Runtime configuration : Choose node selection strategy ( HEALTH_FIRST or RANDOM), set maximum instance count, concurrency, and execution time limits.

For more details, refer to the official PowerJob documentation.