# 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:** 2

<div class="post-metadata">

**Author:** ![LostKobrakai](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/lostkobrakai/32/3072_2.png) [@LostKobrakai](https://forum.elixirforum.com/u/LostKobrakai)\
**Post date:** [June 13, 2025, 8:47am UTC](https://forum.elixirforum.com/t/implementing-distributed-user-counters/71270/2 "2025-06-13T08:47:26Z")

</div>

I guess the big question will be how hard of a constraint that “max 70 people” limit should be. You’re essentially running head on into the complexities of distributed computing with what you’re describing if you need this to be a hard constraint – as in neither disallowing someone to join when there’s less than 70 people as well as not allowing people to join from the moment there are 70 people.

> [@jaybe78](#):
>
> It’s not good for me because I don’t want those rooms to be too crowded. (I plan on using Phoenix Presences on those channels, which does not scale very well when there’s too many users)

I’d love to see any details for that and if that indeed is a problem with large individual channels vs. many users no matter the spread over channels.

---

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