Product questions

Updated at:

What are the core features of Job Scheduling?

  • Distributed scheduling: Enhances system availability and scalability. It separates scheduling from business logic, which allows developers to focus on business logic.

  • Multiple job types: Supports simple jobs, cluster jobs, message jobs, and stream jobs for various scenarios.

  • Comprehensive management features: Includes scheduled triggers, event triggers, manual triggers, graceful stop, resume from breakpoint, configuration import and export, and OpenAPI.

  • Extensive job configuration options: Includes multiple routing policies, retry patterns for failed jobs, and handling policies for missed triggers. It also supports online configuration of job input parameters.

  • Visual job orchestration: Simplifies operations management for multitasking scheduling. It supports various manual operations such as pause, resume, skip, lock, unlock, reset, and retry on failure.

  • Job monitoring: Allows you to view job information in real time. This includes execution status and progress, execution duration, the IP address of the client, success status, and the reason for any failures.

For more information, see Job Scheduling Overview.

What are the application scenarios for Job Scheduling?

Job Scheduling provides unified scheduling for large-scale distributed tasks, which helps businesses accelerate their processes. Typical scenarios include interest settlement, daily cutovers, and balance buffer accounting in the finance industry, along with batch processing of government data.

What job types does Job Scheduling support?

Job Scheduling supports several job types, including simple jobs, cluster jobs. Additionally, the job topology orchestration feature lets you arrange multiple jobs into a topology graph based on their execution order and run them automatically. This simplifies operations management for multitasking scheduling.

For more information, see Features.

What are the development framework requirements for the Job Scheduling client?

The Job Scheduling client does not have specific requirements for development frameworks. You can start development by importing the required Maven dependency package directly into your Java project.

To simplify your development process and experience all the features of the financial technology platform, we recommend that you use the SOFA financial-grade distributed middleware suite to develop your applications. SOFA is a financial-grade distributed middleware developed by Ant Technology. It contains all the components required to build a financial-grade, cloud-native architecture. It is a complete solution for distributed architectures and embodies best practices refined from financial scenarios. SOFABoot is a development framework based on Spring Boot. For more information, see SOFABoot Quick Start.

How is Job Scheduling billed?

The public preview for Job Scheduling has ended. Currently, this component is billed by the number of schedules. It uses a tiered pricing model based on the cumulative number of monthly schedules. The billing unit is CNY per 10,000 schedules.

For detailed billing information, see Pricing.