title: Using cosmos db for Spring batch job repository
body: <p>Is it possible to use CosmosDB as a job repository for Spring Batch?
  If that is not possible, can we go with an in-memory DB to handle our Spring batch jobs?
  The job itself is triggered on message arrival in a remote queue. We use a variation of the process indicator in our current Spring batch job, to keep track of &quot;chunks&quot; which are being processed. Our attributes for saveStep are also disabled . The reader always uses a DB query to avoid picking up the same chunks and prevent duplicate processing.
  We don't commit the message on the queue , till all records for that job are processed. So if the node dies and comes back up in the middle of processing , the same message would be redelivered , which takes of job restarts. Given all this, we have a choice of either coming up with a way to implement a cosmos job repository or simply use in-memory and plug in an &quot;afterJob&quot; listener to clean up the in-memory job data to ensure that java mem is not used in Prod. Any recommendations?</p>