I have a windows scheduler service written in C# that queries a bunch of records from database, performs a set of operations on the data and updates these records back to the database. I now need this service to be deployed on multiple machines. However, the obvious problem I will end up is the concurrency. The service running on multiple machines should not pick up the same records. Is there a pattern/best practice that fits this situation?
Aucun commentaire:
Enregistrer un commentaire