Urgent.News

What's breaking now, across thousands of outlets.

Tech

User Avatar Upload Backend: Database Storage or Local Disk for US/EU Receipt Retention

Short answer: for a user avatar upload backend, keep the original property receipt in private object storage, keep its key and audit metadata in the database, and make deletion a recorded workflow rather than an incidental file operation. For a small US or EU property-management app, that arrangement usually gives the cleanest boundary between transactional data and retained evidence. The…

For a user avatar upload backend, it is recommended to keep the original property receipt in private object storage while storing its key and audit metadata in the database. This approach separates transactional data and retained evidence, providing a clean boundary between the two. The important aspect is to preserve the original file, identify the tenant or property record, and make the retention decision explicit before implementing image processing or adding a second region.

A small US or EU property-management app should follow this arrangement for the cleanest implementation. The table provided offers a decision aid, emphasizing that retention and recovery decisions should be made before considering monthly price. Database blobs are suitable when the file set is tiny, the database backup and restore plan includes the bytes, and the receipt must be committed or deleted in the same transaction as its business row.

However, local disk storage may be simpler for a one-process prototype but becomes less reliable as a source of truth after introducing additional processes or hosts.

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

Other reports of this story

Every outlet that reported this, and when →

Read the original at dev.to →

More in Tech

Code review shouldn't catch import rules: a React Native architecture ESLint enforces

Short answer: Bareship writes its architecture down as lint errors instead of a wiki page. ESLint checks that imports go one way through five layers and that features never import each other, and…

  • Bareship enforces architecture using ESLint lint errors
  • ESLint checks import directions through five layers
  • Dependency-cruiser examines entire import graph in CI

Restaurant Menu Retrieval Architecture in 2026: Freshness Windows and Reranking Trade-offs

The least complex design that stays trustworthy is a staged retrieval pipeline: search fresh sources, query a bounded collection, then rerank only the small candidate set.

  • Restaurant menu retrieval uses staged pipeline with fresh sources and reranking.
  • Explicit freshness window and source context maintained throughout process.
  • Architecture divided into fast and slow clocks with 15-minute freshness window.

How to (not) Destroy Your SSD

37 TeraBytes in three weeks In June 2026 a Codex user opened an issue on the openai/codex repository with a set of numbers that did not seem to belong together.

  • Codex user discovered 37TB SSD writes in 3 weeks
  • SQLite database logging causes SSD wear
  • Apple lacks SSD endurance ratings for MacBooks

More from Monday 16 November →