Hello, I don’t find any common approach to start heavy work or children’s processes after DynamicSupervisor started. When we restart application or DynamicSupervisor is crash, we need to start DynamicSupervisor children’s processes or do heavy work as the handle_continue function when we use GenServer. In our project, we use start_link for this:

defmodule SomeDynamicSupervisor do

  use DynamicSupervisor
  alias SomeGenServer

  def start_link(_) do
    with link <- DynamicSupervisor.start_link(__MODULE__, %{}, name: __MODULE__) do
      Task.async(fn -> start_child_processors() end)
      link
    end
  end

  def init(_) do
    DynamicSupervisor.init(strategy: :one_for_one, max_restarts: 10)
  end

  def start_child_processors do
    SomeLogic.list_of_ids()
    |> Enum.each(&init_processor/1)
  end

  def init_processor(some_id) do
   
    opts = [name: NameGenerator.processor_registry_name(some_id)]

    DynamicSupervisor.start_child(__MODULE__, %{
      id: "#{SomeGenServer}_#{some_id}",
      start: {SomeGenServer, :start_link, [opts]}
    })
  end
end

What pitfalls does this approach have? Perhaps there is a better way. Can anyone share it with me?