Erlang handles best practices?

I built an implementation of a process queue that creates a pool of workflows that receive a message with a payload with a database to work with. When this process is completed, it will send a message back to the pool, and the pool manager will re-run this process identifier for use.

My question is this: is it better to abandon the process and just create a new one? Or recycle it?

+4
source share
1 answer

The design of the process in Erlang is extremely light. Drop and create a new one.

+7
source

All Articles