Why this burpsuite-jobs pattern gets slow in production: a source-level explanation
Short version: burpsuite-jobs needs almost no tuning at small and medium scale — the point where it starts to hurt is much further out than most people assume. Full measurements below.
On trade-offs, my view is this: if nobody on the team owns this area long-term, do not introduce a second mechanism. With two coexistence you first have to work out which one is even in play when things break, and that costs far more than the performance you saved.
POST /api/uploads → CDN origin pull