SShortSingh.
Back to feed

Storage API Rate Limits Stall Private Thumbnail Uploads; Four Retention Rules Proposed

0
·1 views

The article explains that when a storage API rate limit is hit during private thumbnail uploads, the client should slow down, retry HTTP 429 responses with bounded exponential backoff, and record retention and deletion in application-owned data so the storage vendor can be swapped. It notes that failures can originate either in a slow renderer or an overly aggressive storage writer, and that tight retry loops can compound a quota breach. Recommended monitoring focuses on the ratio of completed private objects to upload attempts rather than raw request volume, with alerts tuned to avoid both noisy paging and hidden retention gaps. Suggested practices include capping concurrency, honoring Retry-After headers, using jitter, retrying only the upload rather than the expensive render, and using deterministic object keys with explicit ownership to avoid write conflicts. The piece also promotes a provider, Infrai, as one replaceable adapter, citing its discoverable API surface and single-key billing, while cautioning that adapters still need their own retention logic.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

81 Cross-Chain Swap Apps Compared on Fees, Custody and KYC (October 2026)

A review of 81 cross-chain swap apps was checked live on 10 October 2026, comparing their fees, custody arrangements and identity-check requirements. Only 24 of the 81 publish a fixed fee of their own on a current official page, while 37 publish no rate at all. Wallets proved the costliest option, with a median verified fee of 0.875% versus 0.25% for aggregators, and most of what users pay is the app's markup over the underlying protocol. About 30% of apps hold users' coins during the swap, and 30 apps can hold a swap until the user verifies their identity, even when marketed as no-KYC. The dataset is published openly under CC BY 4.0 and is updated monthly, with the latest re-check dated 18 November 2026.

0
ProgrammingDEV Community ·

Auto-generating Tailwind configs from Figma variables to stop design-code drift

A developer noticed a button component using an arbitrary 18px width because a newly added Figma spacing token was missing from the Tailwind config. The team's Tailwind configuration had gone three months without updates while designers added variables daily. Developers were compensating with hardcoded arbitrary values, undermining the design system. To fix this, the author built a script that exports Figma variables as W3C-format JSON and transforms them into a Tailwind theme object. The TypeScript utility recursively walks the token tree to extract colors and spacing, and it runs in the CI pipeline so the config stays synchronized with design changes.

0
ProgrammingDEV Community ·

Bridging Instant Payment Rails with COBOL Mainframe Ledgers: Precision and Retry Risks

Instant payment systems such as UPI, Pix, SEPA Instant and FedNow process ISO 20022 messages in milliseconds at the front end. Many Tier-1 banks, however, still keep their authoritative ledgers on IBM Z mainframes running CICS, Db2 and COBOL COMP-3 code. The article warns that naive LLM-based code translation can introduce two silent failures: rounding drift when packed-decimal values are converted to binary floats, and double-posting when ISO 20022 timeouts overlap with CICS commits. It proposes mitigations including exact base-10 decoding of COMP-3 sign nibbles, banker's rounding, idempotency keys with outbox reconciliation, and formal equivalence checks. The author also recommends 30-day shadow dual-run parity testing before retiring mainframe capacity.

0
ProgrammingDEV Community ·

Why PowerShell Mailbox Exports Run Slowly and How Offline Processing Helps

Administrators exporting large Exchange Online or Microsoft 365 mailboxes with PowerShell often see throughput of only about 1 GB per hour. Microsoft deliberately throttles these scripts through token buckets, concurrency caps, and disk-latency back-offs to protect shared multi-tenant infrastructure. Compliance Portal eDiscovery exports avoid scripts but split data into fragmented archives, can strip custom categories and flags, and lack resume support. The article describes an alternative that processes PST files directly from disk using multi-threaded binary parsing, which bypasses cloud throttling. It also records progress in a SQLite checkpoint database so interrupted jobs can resume, and computes local hashes and metadata for audit purposes.