Urgent.News

What's breaking now, across thousands of outlets.

Tech

Multipart Upload Selection for Large Private Documents in Node.js

A 1 GB archive that restarts at 99% is an operational problem, not a progress-bar problem. Short answer: use multipart upload when a whole-file retry exceeds the recovery budget or the client must resume; use a single transfer only when a verified restart is acceptably cheap. For private document storage, make the decision before the first byte moves, then prove the stored object exists before…

When dealing with large files like PDFs and ZIPs in Node.js, multipart upload selection is crucial for handling potential interruptions during transfer. The decision to use a single transfer or multipart upload should be made before the first byte moves, considering factors such as retry costs, connection behavior, and client persistence.

For private document storage, it's essential to verify the existence of the stored object before proceeding with OCR, parsing, or embedding. Implementing a Node.js service that issues short-lived permissions for each operation, along with a control-plane worker to validate the object's size and emit a completion event, can help ensure a stable and reliable upload process.

However, it's important to remember that multipart upload is not always the best choice, especially when there is no ownership of expiry and cleanup, as it may lead to unnecessary resource consumption and potential security risks.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Your Contact Form Says Thanks, Then Loses the Lead. Here Is a Next.js Handler That Cannot Drop One

Picture the failure mode that worries me most on a service business site. A homeowner fills out the contact form, clicks Submit, and sees a green "Thanks, we will be in touch." Behind that message…

  • Contact forms are critical for service-based websites to capture leads.
  • Failure to store submissions first can lead to lost leads and false expectations.
  • Storing leads in controlled storage before notifying third-party services prevents silent loss.

Uniface 10 field triggers - leaveField compiles, but loseFocus is what runs

A customer app built in Uniface 10 got a quick entry form: while the user moves from field to field, the form tidies names, checks the e-mail address, fills in the city from the postal code and lists…

  • Uniface 10 renamed interactive field triggers
  • "leaveField" trigger replaced with "loseFocus"
  • Proper trigger names crucial for Uniface 10 functionality

More from Monday 16 November →