This article analyzes multiple engineering solutions for automatically cancelling orders after the payment timeout, covering single‑machine and cluster scheduled‑task designs (Quartz, ElasticJob, XXL‑JOB), delayed‑message techniques (RocketMQ, custom delay service, Redis), and essential concurrency and monitoring best practices.
This article explains why scheduled jobs run twice in a multi‑node deployment, shows how to isolate the timing logic into a single service, and demonstrates using ElasticJob with Zookeeper for sharding, distributed locks, and high‑availability to ensure each task executes exactly once.
This article compares popular Java task scheduling solutions—including Quartz, Spring Schedule with Redis locks, ElasticJob‑Lite, centralized MQ and XXL‑JOB approaches—explaining their core components, clustering strategies, code examples, and practical selection guidance for building reliable distributed schedulers.
This article compares popular Java task scheduling solutions—including Quartz, ElasticJob‑Lite, XXL‑JOB, and custom implementations—explaining their core components, clustering strategies, distributed lock mechanisms, and practical code examples to help engineers choose the right framework for their needs.
This article compares five popular enterprise scheduling solutions—Crontab, Spring Task, ElasticJob, XXLJob, and Serverless Job—by outlining their goals, usage patterns, implementation details, and common pain points, helping architects choose the most suitable option for cloud‑native environments.
This article provides a comprehensive overview of ElasticJob‑Lite, a distributed scheduling solution for high‑concurrency environments, covering its architecture, ZooKeeper‑based registration and sharding mechanisms, core listener components, key code examples, and the UI console deployment.
This article explains the core concepts, architectures and trade‑offs of several Java task‑scheduling solutions—including Quartz, Redis/Zookeeper distributed locks, ElasticJob‑Lite, XXL‑JOB and a self‑built scheduler—while providing code examples and practical guidance for building reliable, scalable job execution systems.
This article explains why Elastic Job tasks can clash in ZooKeeper when they share the same name but different classes, and shows how using the namespace property—especially tying it to the Spring Boot application name—effectively isolates jobs and prevents such conflicts.
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 Java‑based distributed scheduling framework that blends Quartz‑style job timing with ZooKeeper coordination, offering lightweight Lite and cloud‑native Cloud editions, elastic scaling, resource governance, and a roadmap toward Kubernetes support and plug‑in extensibility.
