whitfin/cachex
Cachex is an in-memory key-value caching library for Elixir that manages data storage using Erlang's ETS. It provides a modular architecture with dedicated services for concurrency, expiration, and routing across distributed nodes. The system supports various eviction policies and routing strategies, ensuring consistent and reliable cache operations.
64.4
Adequate · 1 August 2026
6.1k
lines of production code
Elixir
primary language
1
bus factor · 46 authors in all
2
measurements over time
How it got here
2016 · Cachex library introduction and refactoring
This period marks the introduction of the Cachex in-memory cache library, featuring a comprehensive public API backed by ETS. The codebase underwent significant architectural refactoring to separate concerns into dedicated modules for actions, hooks, and routing, while simultaneously establishing a robust test suite to validate the new functionality.
8 changes
2017 · Service-based architecture refactoring
The codebase underwent a significant architectural shift to a service-based model, replacing a monolithic process structure with dedicated GenServer processes for cache management, locking, and notifications. This period also introduced a new specification validator to enforce runtime type checking and added comprehensive test coverage for these new components.
5 changes
2018–2024 · Routing and limit policy expansion
This period focused on expanding the library's capabilities by introducing four new cache routing strategies and three cache limit policies. The work included implementing the routing and limit modules, adding comprehensive test coverage, and updating the benchmarking suite to use the Benchee library.
7 changes
Survey your own repository
whitfin/cachex was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point the surveyor at a repository you know and see whether you agree with it.
About this page
- The description of this project is derived from its own commit history, not from its README.
- The score is its highest published measurement, taken on 1 August 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 44ac7e445b — the exact code this score is about.
- Scored under rubric rubric-2026.08.18. Score the same commit under that rubric and you get the same number.