Fl4m3Ph03n1x
Background
I have an application that upon start creates 100 processes. Now, every time I need to perform a specific operation (say, calculate the size of my ego 
) I pick one of those processes at random to perform the calculation.
So now I need to access those processes, which means I need to save them somewhere, aka, I need state.
State via named ETS tables
This solution advocates that when starting my app, I create all the processes and save their pids into an ETS table with a name (which is a singleton in the end).
This solution is simple, and works as a cache (so far so good), but I really don’t like singletons in my apps because they make for code poorly testable. I could create a mock of the singleton and use it for tests, but I wonder if there is simpler way.
State via GenServer
After reading pragmatic’s Dave approach to components, I understand that he (and some erlangers) prefer to manage state via GenServers. This would mean I need processes to communicate with this GenServer and would add a lot of boiler plate code to my app, not to mention I believe this is quite overkill for the problem at hand - I just want a table of pids after all.
Questions
So this brings me to a couple of questions:
- Are there other ways to manage State in Elixir?
- Which approach (ets or genserver) would you choose and why?
PS: the size of my ego is the same as the size of my intelligence: NaN (so small doesn’t even qualify 
)
Where Next?
Trending in Discussions
Other Trending Topics
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
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Practical resources that improve the lives of professional developers.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Most Liked- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kokolegorille
Why not use Registry?
shanesveller
I would say that this isn’t a question of state so much as of process registration. The workers themselves sound stateless in your description. Any one of them is capable of fulfilling a request, and none of the persist or share anything between subsequent requests.
Read up on how GenServer’s allow various forms of name registration. Next, take a look at
:globalfrom Erlang andRegistryfrom the Elixir stdlib. If you just need a constant-sized worker pool where any of them are used to handle a given single invocation, look at the:poolboyErlang library. One of these should fit your use-case.https://github.com/devinus/poolboy
benwilson512
How would the process get a command if not by receiving a message? Notably if they’re inside a registry you don’t also need
pg2, you can use Registry to broadcast, there are examples in the registry docs.Last Post!
bottlenecked
This still sounds like poolboy to me- unless each connection is to a different endpoint, in which case process registration like other people mentioned here would work better. But if you connect to the same (or just a couple) different endpoints and do not wish to pay upfront the cost of opening 10000 connections, you can do that lazily with poolboy using a small size with a large max overflow