Best Practice For Job Repository - Shared Common Repository or Multiple Repositories?
I have a quick question to advise on how we should setup our job repositories in particular to support a broader rollout across a large enterprise. Is it ok to setup a common single job repository that we can share between multiple applications? The idea being this would be a managed service to help reduce the overall infrastructure required and to have a single point to monitor jobs.
My main concerns are around concurrency + ensuring rogue applications don't bring down the overall managed service. Any insight into the general scalability of a single repository would be appreciated.