Caching, Queues & Background Jobs

Caching strategies, job queues, retries, and background processing patterns.

  • 4 Tracked terms
  • Last 30 days Feed window

What this topic collects on

An article joins this feed when it matches these terms. Each one is also a search of its own.

Latest in Caching, Queues & Background Jobs


dev.to > isurajmisra > a-cache-with-no-way-back-to-the-source-5dja

A cache with no way back to the source

10+ hour, 57+ min ago   (346+ words) Checkout deliberately asks for nothing but a URL — no title field on the add-listing form. So a listing's name doesn't exist yet the moment money lands; it's filled in later, two different ways depending on the listing: That part works....


dev.to > alexgeorgiev17 > redis-810s-compact-hashes-need-himport-or-a-restart-to-kick-in-hj8

Redis 8.10's compact hashes need HIMPORT or a restart to kick in

12+ hour, 19+ min ago   (769+ words) I ran Redis 8.10.1 in Docker and tested it against two schemas, a throughput benchmark, a concurrency check, and the two ways to actually trigger the new encoding: the new HIMPORT command, and a server restart. Redis 8.10 adds hash templates: an…...


hackernoon.com > i-argued-with-an-interviewer-about-global-rate-limiting-neither-of-us-were-right

I Argued With an Interviewer About Global Rate Limiting. Neither of Us Were Right

16+ hour, 24+ min ago   (1397+ words) Global rate limiting has a conservation law. Once you see it, most of the architectural debate disappears. The interviewer suggested a broadcast mechanism to share counts between regions. I pushed back. It sounded over-engineered for rate limiting: a lot of…...


medium.com > @ios-interview > lazy-loading-vs-prefetching-best-practices-for-tableviews-db342b37813a

Lazy Loading vs. Prefetching: Best Practices for TableViews 🚀

13+ hour, 21+ min ago   (26+ words) When you’re dealing with large datasets in iOS — feeds, chat histories, search results — performance stops being optional. Two …...


dev.to > yass1n > brojs-v240-redis-clustering-api-key-rotation-and-a-rate-limiter-that-actually-survives-4pja

bro.js v2.4.0 - Redis clustering, API key rotation, and a rate limiter that actually survives outages

22+ hour, 8+ min ago   (130+ words) Pushed v2.4.0 of bro.js (my zero-boilerplate Express alternative) and figured I'd write up what changed instead of just dumping a changelog. Used to be you had to wire up your own Redis client and babysit connection state. Now you just…...


medium.com > @bikisahu161 > redis-the-backend-sidekick-that-makes-your-application-fast-432f2e831a1a

Redis: The Backend Sidekick That Makes Your Application Fast ⚡

18+ hour, 54+ min ago   (143+ words) What Redis actually is, why everyone talks about it, and where it fits in a real-world backend. When I first heard about Redis, I had …...


dev.to > anusha_mukka > your-cache-is-part-of-the-security-model-44n2

Your Cache Is Part of the Security Model

1+ day, 16+ hour ago   (418+ words) This is Part 4 of Security Infrastructure in Practice, a series about what happens when security design meets production systems. Caches are supposed to make authorization faster. They can also keep an old permission alive after the source of truth has…...


dev.to > mech_app_ai > agent-cache-multi-tier-llm-caching-for-valkey-and-redis-10kf

Agent-Cache: Multi-Tier LLM Caching for Valkey and Redis

1+ day, 20+ hour ago   (666+ words) Agent loops burn tokens and clock cycles on repeated work. The same LLM prompt fires twice, the same tool call fetches identical data, and session state gets reconstructed from scratch on every request. Agent-cache solves this with a three-tier caching…...


dev.to > webmatrixlab > api-rate-limiting-what-actually-breaks-when-you-get-it-wrong-3dip

API Rate Limiting: What Actually Breaks When You Get It Wrong

1+ day, 21+ hour ago   (417+ words) Most teams add rate limiting to their API as an afterthought — usually right after something has already gone wrong. A scraper hammers an endpoint, a client integration goes into a retry loop, or a single misbehaving user takes down a…...


dev.to > mohammad_abdullah121 > redis-is-not-your-database-designing-cache-failures-fallbacks-and-resilient-backends-15op

Redis Is Not Your Database: Designing Cache Failures, Fallbacks, and Resilient Backends

2+ day, 2+ hour ago   (724+ words) Redis can make a backend dramatically faster. It can also make a backend dramatically more fragile if the architecture treats the cache as a dependency that must always be available. The distinction is simple: A database stores authoritative data. A…...