If it's just a small fire and forget thing in Erlang, you can just spawn the process, sure. My point is that once people start to care about what happens with those background jobs, you probably need some infrastructure around them, and then the Erlang thing might start to resemble Sidekiq a bit more.
"When we want to have more control, i.e. persistence on disk, a workers pool, retries, among other things, there are several popular solutions:
Oban: a robust PostgreSQL-based queue backend process system. It has a UI in its pro version
Exq: a Redis-based Resque and Sidekiq compliant processing library. It has an open source UI exq_ui
verk: same as Exq. Is is compatible with Resque and Sidekiq job definitions"
