Short answer: upload the original image from the browser straight to private object storage, finalize it in the backend, and put a small job on a Node.js queue for thumbnail generation. Use a storage notification or webhook only as a delivery signal. The backend database remains the authority for tenant access and processing state.
That split keeps large bytes away from the application process. It also gives every retry a clear boundary. The browser moves bytes. The API grants a narrowly scoped upload. A worker reads a finalized original and writes deterministic thumbnail keys. A notification wakes the worker; it does not grant permission.
I choose this shape for a gaming media pipeline where players upload large screenshots or clips and the UI needs a quick preview. I've learned to draw the trust boundary before choosing a queue library.…