Resumable file uploads with plain Jakarta EE and TUS protocol
Plain uploads break when connections drop. The TUS protocol fixes that with resumable uploads. Here we will implement it with pure Jakarta REST using POST, HEAD, PATCH, and a few headers.
Use ↑ ↓ to navigate, ↵ to open, Esc to close.
Senior Technologist & Architect.
Community Builder. Speaker.
I build complex, business-critical solutions that work in practice, and speak globally about cloud, architecture, AI, and security.
Helping teams design and build business-critical systems – cloud architecture, modernization, secure platforms, and delivery pipelines that scale and last.
Engaging talks and keynotes worldwide on cloud, architecture, AI, and security. Hands-on workshops and deep-dive training.
Lead organiser of Google Developer Group (GDG) Cloud Oslo. Working with GDGs and JUGs worldwide to grow and connect developer communities.
Plain uploads break when connections drop. The TUS protocol fixes that with resumable uploads. Here we will implement it with pure Jakarta REST using POST, HEAD, PATCH, and a few headers.
How to build a REST API that accepts binary attachments? As part of a multipart payload, or as the whole body. Standard Jakarta REST 3.1 EntityPart, the Quarkus @RestForm approach, and the raw application/octet-stream case, with code examples and the usual pros and cons.
What happens when a JSON response contains more fields than your DTO declares? The answer depends on your JSON provider. A look at the defaults for JSON-B, Jackson, Quarkus, and Spring when consuming an API with the MicroProfile REST Client – with the official docs to back each one up.