Alternatives
Products that do what Layercache does
Stop DDOS-ing your own database.
- 1
- 2SA
Last night, while trying to figure out the best way to implement caching in my app, I had an idea for a dirt-simple caching system based on a dependency graph. The premise I started with is that one of the hardest things to manage in a cache is dependencies between entities. In order to cache items effectively, you inevitably have to duplicate "child" data inside of "parent" entries. Then, when a child is changed, you have to invalidate the child and its parents, and its parents' parents, and so on. To try to help this, I hacked together a simple Node.js library called Stash, which models…
2012
- 3FC
2024 · determinate.systems
- 4PP
Hey all, I recently published this Go package, and would like to show off as well as get feedback!
2024 · github.com
- 5CH
Jan 2026 · github.com
- 6RA
2013 · redstone.io
- 7DN
2015 · github.com
- 8PF
2025 · github.com
- 9CM
2025 · github.com
- 10RS
2016 · github.com
- 11AL
Raymond here from Butter.dev, an LLM response cache built as a chat-completions proxy. Today we're launching a key feature for the platform: the ability to generalize on dynamic, templated inputs. Caching at the HTTP request level has the obvious problem of generalizability. Nearly no request is identical, due to templated variables (like names) and metadata (like timestamps), so exact-match cache lookups rarely hit. We solve this at Butter by using LLMs to detect dynamic content in requests and derive their inter-relationships, allowing the cache entry to be stored as a template + variables…
Jan 2026 · blog.butter.dev
- 12CH
Hi, I'm fiiv, and I'm the creator of Cache Horse. I built it because I wanted an easy plug-n-play solution to caching and simplifying HTTP requests - in particular, on frontend. First, I was fetching data like daily weather, historic currency exchange numbers, air quality readings - and many of those APIs have quota limits. And second, since I was already caching them, I thought it would be useful to batch them together - so I built that feature in. I would love to hear your feedback and thoughts on the project. Thanks!
2025 · cache.horse
- 13CJ
2015 · yangmillstheory.github.io
- 14IM
Primarily built this to learn how NextJS works and also a bit about Tailwind CSS. Also has request caching using the WebCache API + expiration which is quite a hacky implementation. Let me know what you think! Source is at https://github.com/say4n/hn, pull requests welcome!
2023 · hn.sayan.page
- 157R
2021 · github.com
- 16GL
2019 · github.com
- 17QF
2025 · github.com
- 18SA
2018 · npmjs.com
- 19OS
2022 · wundergraph.com
- 20AC
Multi-tier exact-match cache for AI agents backed by Valkey or Redis. LLM responses, tool results, and session state behind one connection. Framework adapters for LangChain, LangGraph, and Vercel AI SDK. OpenTelemetry and Prometheus built in. No modules required - works on vanilla Valkey 7+ and Redis 6.2+. Shipped v0.1.0 yesterday, v0.2.0 today with cluster mode. Streaming support coming next. Existing options locked you into one tier (LangChain = LLM only, LangGraph = state only) or one framework. This solves both. npm:…
Apr 2026
- 21FC
2019 · github.com
- 22SI
Have a look at my semantic caching project! It's built to easily integrate in existing LLM workflows, you can use it as a proxy where the cache forwards missed requests without modification to a specified upstream, automatically updating it's cache with the response. You can also use it as a cache-aside cache with a provided python library. It works by computing embedding vectors of input queries, and matches them to seen query + response pairs using a vector store. Everything is in-memory, so it should be blazing fast :)
2025 · github.com
- 23EG
2018 · stackshare.io
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →