reads straight forward to me...
have a database with the file id, path, user and status and update it there.
Upload: put file to storage, insert DB: FileId/Path, user, "waiting for processing"
You also have built a queue, so the on-premise job can go into the db, load the file and update the status to "processing".
When done, upload the file and update the database with "maybe new file path", "Processed".
Not sure, why the processing job needs to be on premise, you could have it in the cloud as well using docker or just some PaaS.
With Azure (dont know about other clouds) you could even trigger an AzureFunction (and from there a WebJob) with the upload using an EventTrigger.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
reads straight forward to me...
have a database with the file id, path, user and status and update it there.
Upload: put file to storage, insert DB: FileId/Path, user, "waiting for processing"
You also have built a queue, so the on-premise job can go into the db, load the file and update the status to "processing".
When done, upload the file and update the database with "maybe new file path", "Processed".
Not sure, why the processing job needs to be on premise, you could have it in the cloud as well using docker or just some PaaS.
With Azure (dont know about other clouds) you could even trigger an AzureFunction (and from there a WebJob) with the upload using an EventTrigger.