File upload and store, then proccessing with remote worker
There are few interesting options.
As example, you can add additional reupload workers step for deploy process. It'll guarantee
 consistence between deployed application and workers.
Using own (rest) api is great idea, i like it even more than sharing models between different beings
My question is about web application architecture.
I have a website, my users can upload files and from this files I need to create some kind of reports for users. When user upload file it stored on my server where website hosted. File path stored in Django model field. Worker is on another server and i need to get access to my database and procces that file. I know how to use django ORM itself without URLs and other parts of django. 
My question: If I need to create workers on another server, which use different django models from my website i need to copy all of the models into every worker?
For example, one worker proccess file and it need models "Report" and "User". Other worker do other actions and need "User" and "Link" models. Everytime i change model in my main website i need to change same models in my workers, also different workers can have same duplicate models. I think it's not good from architecture point.
Any suggestions on how to organize my website and workers?