XXL-JOB framework overview illustration prompt

Create a clean 16:9 editorial architecture illustration for a Chinese source-analysis article about XXL-JOB. Show the whole framework rather than one API call.

Composition:

• Left: an “Admin / Scheduling Center” control plane with task management, a 5-second database pre-read scanner, a 60-slot time wheel, fast and slow trigger pools, routing, retry and alarm.
• Center bottom: a MySQL database shared by task configuration, executor registry, schedule lock and execution logs. Make the schedule lock visible as a single coordination gate.
• Right: several business applications embedding “Executor / xxl-job-core”. Inside each executor show Netty HTTP endpoints, a per-job JobThread queue, Java @XxlJob handlers, optional Groovy or scripts, local log files and callback retry files.
• Directional flow: Admin sends POST /trigger to an executor; executors send /api/registry heartbeats and /api/callback results to Admin. Handlers connect to generic business databases, HTTP APIs and file systems.
• Top: an operator and OpenAPI client entering the Admin management layer.
• Make failure boundaries readable: routing failure, execution failure and callback failure are separate checkpoints.

Visual style:

• Professional but approachable technical editorial diagram, dark navy and warm orange accents on an off-white background.
• Clear spatial hierarchy, restrained labels, no code screenshots, no fake metrics, no company logos beyond the text “XXL-JOB”.
• Use Chinese labels for major roles and short English identifiers only where they are actual concepts: Admin, Executor, MySQL, JobThread, HTTP.
• Emphasize control flow and role separation; avoid decorative server racks or generic cloud imagery.
• The generated image is conceptual. Exact module relationships and call order remain in Mermaid diagrams in the article.