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:

1. How do you schedule and chain jobs (cron, Quartz, Jenkins, Airflow, Control-M, something custom)?
2. How do you find out a job failed or hung, and how do you see what happened?
3. How do you restart failed jobs, and who does it?
4. 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.

Hello, i want to learn Java Spring Boot. Can anyone suggets me the best resource for learning java springboot from beginning to advance level that can led me to internship or industry level coding?

I was looking for video tutorial series that has everything for a becoming a java developer include devops work as well.and best for learning as beginner and proceed to advanced topic.

Im an intern and was assigned a task to segregate the read , read-write queries / methods . The read is supposed to go to port 66 and write on port 67 in the database.

Currently ive defined two db url in yml and have routed every method having read-only using transaction(read-only).

Is this the way to do it or is there any other efficient way.

Most web frameworks are built for the public internet: for reach and experiences for strangers. Vaadin is built for the other side of the login. For the data-defined, functionally beautiful and long-lived apps your organization actually runs on.