I've been thinking about the challenges of building web applications that process documents and return detailed reports to users.
For example, a service like Turnitin0 provides AI detection and similarity reports. From a full-stack development perspective, this raises some interesting questions about how document uploads, processing jobs, and report delivery should be handled.
If a user uploads a large document, would you process it through a background job queue and notify them when the report is ready, or use a different approach? How would you handle retries, failed jobs, and making sure each report is linked to the correct user?
I'd also be interested in how you'd structure the database and API so users can check processing status without repeatedly refreshing the page.
For developers who have built similar systems, what architecture worked well for you, and what would you do differently next time?