processDefault(objs);
            break;
        }
    }

    /**
     * Processes default log events (no specific handling).
     *
     * @param objs the log objects
     */
    protected void processDefault(final Object... objs) {
    }

    /**
     * Processes system error log events.
     *
     * @param objs the log objects (should contain a Throwable)
     */

If you check out the "task manager" or "system monitor" (or similar tools) in your operating system, you will be able to see many of those processes running.

And, for example, you will probably see that there are multiple processes running the same browser program (Firefox, Chrome, Edge, etc). They normally run one process per tab, plus some other extra processes.

A container is running as long as the **main process** (command or program) is running.

A container normally has a **single process**, but it's also possible to start subprocesses from the main process, and that way you will have **multiple processes** in the same container.

But it's not possible to have a running container without **at least one running process**. If the main process stops, the container stops.

Esos worker processes serían los que ejecutan tu aplicación, realizarían los cálculos principales para recibir un **request** y devolver un **response**, y cargarían cualquier cosa que pongas en variables en RAM.

<img src="/img/deployment/concepts/process-ram.drawio.svg">

Y por supuesto, la misma máquina probablemente tendría **otros procesos** ejecutándose también, aparte de tu aplicación.

        }
    }

    /**
     * Processes allowed SIDs (Security Identifiers) and adds them to the SID set.
     * If the SID is a group, it recursively processes all group members.
     *
     * @param file the SMB1 file
     * @param sid the SID to process
     * @param sidSet the set of SIDs to add to
     */

     */
    public DefaultResponseProcessor() {
        // Default constructor
    }

    /**
     * Processes response data based on HTTP status code and configured transformer.
     *
     * @param responseData the response data to process
     */
    @Override
    public void process(final ResponseData responseData) {
        if (isNotModified(responseData)) {

        }
    }

    /**
     * Processes allowed SIDs (Security Identifiers) and adds them to the SID set.
     * If the SID is a group, it recursively processes all group members.
     *
     * @param file the SMB file
     * @param sid the SID to process
     * @param sidSet the set of SIDs to add to
     */

                }
            }
        }
        return true;
    }

    /**
     * Processes the response data using the appropriate rule processor.
     * @param urlQueue The URL queue entry.
     * @param responseData The response data to process.
     */
    protected void processResponse(final UrlQueue<?> urlQueue, final ResponseData responseData) {
        // get a rule

Tener otro gestor de procesos dentro del contenedor (como sería con múltiples workers) solo añadiría **complejidad innecesaria** que probablemente ya estés manejando con tu sistema de cluster.

### Contenedores con Múltiples Procesos y Casos Especiales

Por supuesto, hay **casos especiales** donde podrías querer tener **un contenedor** con varios **worker processes de Uvicorn** dentro.

            } catch (Exception e) {
                log.error("Error during witness unregistration", e);
            }
        });
    }

    /**
     * Processes a received witness notification.
     *
     * @param notification the notification to process
     */
    public void processNotification(WitnessNotification notification) {