What’s New in ElasticJob 3.0.0‑alpha? Features, API Changes, and Release Highlights
ElasticJob 3.0.0‑alpha introduces a Spring Boot starter for ElasticJob‑Lite, one‑time tasks, expanded database support for execution logs, environment‑variable IP declaration, and several API changes including a new Maven groupId, package name, namespace, SPI‑based job types, and modular UI separation.
ElasticJob is a distributed scheduling solution that provides task sharding, elastic scaling, automatic discovery, and support for time‑driven, data‑driven, resident, and temporary tasks, along with fault detection, automatic recovery, failover, retry, and a comprehensive management platform. After three years of inactivity, the project was revived on 2020‑05‑21.
3.0.0‑alpha Release
New Features
Added a Spring Boot starter for ElasticJob‑Lite.
Introduced one‑time task type.
Extended execution record persistence to support more database types.
Supported IP declaration via environment variables.
API Changes
Changed Maven groupId to org.apache.shardingsphere.elasticjob.
Changed package name to org.apache.shardingsphere.elasticjob.
Updated Spring namespace to http://shardingsphere.apache.org/schema/elasticjob.
New job API using SPI to customize job types.
Introduced SPI for configuration strategies.
Separated console and UI from the core job module.
References
ElasticJob: https://github.com/apache/shardingsphere-elasticjob
Distributed scheduling project ElasticJob is set to restart: https://u.nu/-hu3l
ElasticJob 3.0 new features discussion: http://t.cn/A6USVxXZ
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java Architecture Diary
Committed to sharing original, high‑quality technical articles; no fluff or promotional content.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.