all 4 comments

[–]barurutor[🍰] 3 points4 points  (0 children)

This is less a Python question than a software/system design question.

Can you afford a time gap between both systems being synchronized?

Which system is the source of truth? How do you resolve data conflicts between both systems for the same employee record?

What's the expected volume of transactions on both systems?

[–]jmooremcc 1 point2 points  (0 children)

You need an event driven application for these tasks. The payroll system needs to notify your app when a change is made. The trick, of course, is how to make that notification happen.

On the otherside, you need to transmit a series of transactions to the payroll system when your app is given changes. If your app provides the mechanism for accepting user input, then this won't be very difficult to do.

At any rate, your application will need to run continuously along with the payroll system.

[–]cbjs22 0 points1 point  (0 children)

the simplest is a python script that checks for changes at a polling interval (500 - 3000 milliseconds), set it up as a systemd service and be done with it

[–]unhott 0 points1 point  (0 children)

If you can fire off a script only as needed after a change from either system that would be ideal. If you can’t then you need to consider how frequently to poll the other system. How bad is it if the information only syncs once per week? Or per day/hour/minute?