jamilabreu
Background: I’m looking to build an app that calculates a user’s “friends”, “friends of friends”, and “friends of friends of friends” - basically on every HTTP request.
Question: If this list if associated users could get really long (only grows over time) - would it be more performant to perform a database query each time, or use an approach where each user has their own process/GenServer where the list lives? If the second, any resources or direction on how to best think about / architect this?
Thanks!!!
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Catch errors, track performance, monitor hosts and more.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #ai
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 3- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
aenglisc
You could cache the results in an ets, for one.
hauleth
Do you need list of that friends or you just count them? If you need only count them, then you can denormalise your DB or create materialised views that you will refresh periodically.
OvermindDL1
This is more the realm of graph databases. You can ‘do’ it in postgresql by adding a graph extension or more slowly faking it via path encoding (though that will require 9 extra fields to do efficiently I think?) or slightly less performant by row-caching in postgresql the known friends with triggers to update over time.