strictly speaking it's not needed, however, you probably don't want to do that because raw erlang processes are single threaded with no shared memory (but also

strictly speaking it's not needed, however, you probably don't want to do that because raw erlang processes are single threaded with no shared memory (but also no transactional locking, mutexes, or channels to worry about!) so at a certain scale you will become bottlenecked on that one process. ETS tables (an internal k-v lookup system) cheats a bit on the "no shared memory" rule, and Registry is backed by that and able to be a high-performance solution for sharding your path to the process that needs to handle.