Caching, Queues & Background Jobs

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

  • 4 Tracked terms
  • Last 30 days Feed window
Search within this topic Ask AI about this topic All topics

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 > stark_zhuang_df5076f35c68 > 1551-elasticsearch-and-1462-memcached-endpoints-two-cache-layers-with-different-defaults-4eo6

1,551 Elasticsearch and 1,462 Memcached Endpoints: Two Cache Layers With Different Defaults

8+ hour, 18+ min ago   (836+ words) Two ZoomEye host searches collected on 18 September 2026 returned 1,551 observable services on port 9200 and 1,462 on port 11211. Port 9200 is Elasticsearch's HTTP interface. Port 11211 is Memcached's default listener. The counts are similar; the security stories are not. Elasticsearch: authentication that became a default…...


dev.to > dinukashavi > i-rate-limited-an-api-by-hand-then-i-configured-one-in-a-form-field-365d

I Rate-Limited an API by Hand. Then I Configured One in a Form Field.

23+ hour, 21+ min ago   (285+ words) My hotel booking backend has an GET endpoint that has no rate limiting at all, nothing stops a client... Tagged with api, backend, security....


medium.com > javarevisited > lazy-vs-eager-cache-population-which-caching-strategy-should-you-use-6370a810cde4

Lazy vs Eager Cache Population: Which Caching Strategy Should You Use?

2+ day, 10+ hour ago   (30+ words) Learn the difference between lazy and eager cache population, their performance trade-offs, and how to choose the right caching …...


dev.to > hancic128 > cache-invalidation-three-patterns-and-the-cost-of-getting-it-wrong-2kc0

Cache Invalidation: Three Patterns and the Cost of Getting It Wrong

2+ day, 17+ hour ago   (278+ words) A version-control service I worked on kept a small list in Redis: which version of the code bundle... Tagged with caching, distributedsystems, backend, consistency....


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

A cache with no way back to the source

5+ day, 21+ hour 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....


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

6+ day, 2+ hour 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 🚀

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


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

Your Cache Is Part of the Security Model

1+ week, 2+ 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+ week, 6+ 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 > aniruddhagawali > i-thought-redis-would-save-my-api-just-500-requests-proved-me-wrong-1kam

I Thought Redis Would Save My API. Just 500 Requests Proved Me Wrong.

1+ week, 13+ hour ago   (243+ words) As our series continues, Deep-Dive Backend Systems Roadmap. I created the simplest weather API... Tagged with webdev, distributedsystems, redis, programming....