Why PowerJob Is the Next‑Gen Distributed Scheduling Framework for Java

Overview

PowerJob is a new‑generation distributed task scheduling and computation framework that supports CRON, API, fixed‑frequency, and fixed‑delay strategies, provides workflow orchestration for task dependencies, and simplifies both job scheduling and complex distributed computations.

Why Choose PowerJob?

Popular job scheduling frameworks such as Quartz, elastic‑job (based on Quartz), and XXL‑Job have notable drawbacks.

Quartz, as the first‑generation scheduler, lacks a web UI, requires API‑only configuration, is not user‑friendly, and only supports single‑node execution, failing to leverage cluster resources.

XXL‑Job, a second‑generation scheduler, improves on Quartz but still suffers from limited database support (MySQL only), constrained distributed computing (static sharding only), and no workflow capabilities for DAG‑style task dependencies.

PowerJob Features

Simple usage with a web UI for visual task management, monitoring, and log viewing.

Comprehensive timing strategies: CRON, fixed frequency, fixed delay, and API.

Rich execution modes: standalone, broadcast, Map, and MapReduce, enabling cluster‑wide distributed computation with minimal code.

DAG workflow support for visual task dependency configuration and data passing between upstream and downstream tasks.

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

Operational convenience with real‑time log display in the web console, reducing debugging effort.

Lightweight dependencies: only relational databases (MySQL, PostgreSQL, Oracle, SQL Server) are required, compatible with all Spring Data JPA databases.

High availability and performance through lock‑free scheduling and horizontal scaling of multiple servers.

Fault tolerance with configurable retry strategies and automatic recovery when executor nodes are available.

Product Comparison

Applicable Scenarios

Scheduled tasks such as nightly data sync or report generation.

Broadcast execution across all machines, e.g., cluster‑wide log cleanup.

Distributed processing of large data sets using Map/MapReduce to accelerate computation.

Overall Architecture

Quick Start

PowerJob consists of a scheduling server (powerjob‑server) and an executor (powerjob‑worker). The server provides web services and task scheduling, while the worker executes user‑written task code and offers distributed computing capabilities.

Initialize Project

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

Import the project into an IDE, start the scheduling server, and develop custom processors in the samples module.

Start Scheduling Server

Create a database named powerjob‑daily.

Modify the configuration file (e.g., application‑daily.yml) to set the JDBC URL, username, and password for MySQL (or MongoDB URI for the full version).

oms.env=DAILY
logging.config=classpath:logback-dev.xml

####### Database Configuration #######
spring.datasource.core.driver-class-name=com.mysql.cj.jdbc.Driver
spring.datasource.core.jdbc-url=jdbc:mysql://remotehost:3306/powerjob-daily?useUnicode=true&characterEncoding=UTF-8
spring.datasource.core.username=root
spring.datasource.core.password=No1Bug2Please3!
spring.datasource.core.hikari.maximum-pool-size=20
spring.datasource.core.hikari.minimum-idle=5

####### MongoDB Configuration (optional) #######
spring.data.mongodb.uri=mongodb://remotehost:27017/powerjob-daily

####### Mail Configuration (if needed) #######
spring.mail.host=smtp.163.com
spring.mail.username=zqq
spring.mail.password=qqz
spring.mail.properties.mail.smtp.auth=true
spring.mail.properties.mail.smtp.starttls.enable=true
spring.mail.properties.mail.smtp.starttls.required=true

####### Retention Settings #######
oms.log.retention.local=1
oms.log.retention.remote=1
oms.container.retention.local=1
oms.container.retention.remote=-1
oms.instanceinfo.retention=1

####### Cache Settings #######
oms.instance.metadata.cache.size=1024

Run the main class com.github.kfcfans.powerjob.server.OhMyApplication to start the server and verify the web UI at http://127.0.0.1:7700/.

Register an application via the UI (e.g., oms-test) and set a console password.

Write Sample Code

Enter the powerjob-worker-samples module, adjust the configuration to connect to the server, and implement your own processor.

Update OhMySchedulerConfig with the registered app name.

@Configuration
public class OhMySchedulerConfig {
    @Bean
    public OhMyWorker initOMS() throws Exception {
        // Server HTTP address (port is server.port, not ActorSystem port)
        List<String> serverAddress = Lists.newArrayList("127.0.0.1:7700");

        // 1. Create configuration
        OhMyConfig config = new OhMyConfig();
        config.setPort(27777);
        config.setAppName("oms-test");
        config.setServerAddress(serverAddress);
        // Use in‑memory store if no heavy Map/MapReduce needs
        config.setStoreStrategy(StoreStrategy.MEMORY);

        // 2. Create Worker and set config
        OhMyWorker ohMyWorker = new OhMyWorker();
        ohMyWorker.setConfig(config);
        return ohMyWorker;
    }
}

Implement a processor, e.g., using the basic processor:

@Slf4j
@Component
public class StandaloneProcessorDemo implements BasicProcessor {

    @Override
    public ProcessResult process(TaskContext context) throws Exception {
        OmsLogger omsLogger = context.getOmsLogger();
        omsLogger.info("StandaloneProcessorDemo start process, context is {}.", context);
        System.out.println("jobParams is " + context.getJobParams());
        return new ProcessResult(true, "process successfully~");
    }
}

Run the sample application com.github.kfcfans.powerjob.samples.SampleApplication and verify the console output.

Task Configuration and Execution

After both the server and sample project are running, open the web UI at http://127.0.0.1:7700/ to create and run tasks.

Enter the registered application name on the homepage to access the management console.

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

After creation, run the task immediately via the “Run” button.

View task status and live logs in the side panel.