# Implementing distributed user counters

**URL:** <https://forum.elixirforum.com/t/implementing-distributed-user-counters/71270>\
**Category:** Questions\
**Tags:** distributed, phoenixtracker, pheonix-presence\
**Created:** [June 13, 2025, 8:02am UTC](https://forum.elixirforum.com/t/implementing-distributed-user-counters/71270 "2025-06-13T08:02:14Z")\
**Posts on this page:** 1\
**Showing post:** 23

<div class="post-metadata">

**Author:** ![jaybe78](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/jaybe78/32/36069_2.png) [@jaybe78](https://forum.elixirforum.com/u/jaybe78)\
**Post date:** [June 15, 2025, 8:49am UTC](https://forum.elixirforum.com/t/implementing-distributed-user-counters/71270/23 "2025-06-15T08:49:19Z")

</div>

From the words of the maintainer of Cachex

> The intent for Cachex has always been caching of data; I do not intend to get into the world of supporting distributed databases. The idea of adding “distributed” caches in the first place was so a newly added Node B would be able to fetch pre-warmed data from Node A. If a user wants persistent distributed cache, the answer exists with (e.g.) Redis and Cachex being a local hot layer over a single remote

---

_[View the full topic](https://forum.elixirforum.com/t/implementing-distributed-user-counters/71270)._