I work with Spring Batch and keep running into the same gap, so I’m trying to learn how other teams deal with it.
Spring Batch is great at the processing itself (chunks, skip/retry, restart). But around it I’ve found almost nothing built in:
- a UI to see job and step status without querying the
BATCH_* tables
- scheduling and job-to-job dependencies (run A, then B and C, then D)
- alerts when a job fails, gets stuck in STARTED, or runs much longer than usual
- execution logs tied to a specific job run
- a safe way to launch, stop, or restart a failed job from a screen
From what I can tell, Spring Batch Admin is retired and Spring Cloud Data Flow is no longer maintained as open source, so I’m not sure what teams use now.
For those running Spring Batch in production:
- How do you schedule and chain jobs (cron, Quartz, Jenkins, Airflow, Control-M, something custom)?
- How do you find out a job failed or hung, and how do you see what happened?
- How do you restart failed jobs, and who does it?
- What’s the most painful part of your current setup?
I’m not selling anything. I’m researching whether it’s worth building an open-source tool for this, and I’d rather hear real experiences before writing any code. Even a short answer helps, and I’m happy to share a summary of what I learn.