I think there is potential for a starter in this area. There is alredy an admin client for Spring Batch but it get's all its information from the database direct. It therefore assumes that if you have multiple batch servers running that they are all sharing a database. In a more microservice orientated world I wonder if this will always be the case.
This issue is a spike to see if there are any fruits here. I don't personally know batch well enough and we also have some use cases from my current project to throw at it.
My thinking is roughly:
Register batch servers with Eureka
Starter to expose API for batch server
Batch admin client starter that uses Eureka to discover batch servers to administer and does so via the API
I think there is potential for a starter in this area. There is alredy an admin client for Spring Batch but it get's all its information from the database direct. It therefore assumes that if you have multiple batch servers running that they are all sharing a database. In a more microservice orientated world I wonder if this will always be the case.
This issue is a spike to see if there are any fruits here. I don't personally know batch well enough and we also have some use cases from my current project to throw at it.
My thinking is roughly: