import org.apache.maven.api.services.ModelProblemCollector;

/**
 * Handles profile injection into the model.
 *
 */
public interface ProfileInjector {

    /**
     * Merges values from the specified profile into the given model. Implementations are expected to keep the profile
     * and model completely decoupled by injecting deep copies rather than the original objects from the profile.
     *

/**
 * Handles expansion of general build plugin configuration into individual executions.
 *
 */
public interface PluginConfigurationExpander {

    /**
     * Merges values from general build plugin configuration into the individual plugin executions of the given model.
     *
     * @param model The model whose build plugin configuration should be expanded, must not be <code>null</code>.

import org.apache.maven.api.services.ModelProblemCollector;

/**
 * Handles injection of dependency management into the model.
 *
 */
public interface DependencyManagementInjector {

    /**
     * Merges default values from the dependency management section of the given model into itself.
     *
     * @param model The model into which to merge the values specified by its dependency management sections, must not

import org.apache.maven.api.services.ModelProblemCollector;

/**
 * Handles inheritance of model values.
 *
 */
public interface InheritanceAssembler {

    /**
     * Merges values from the specified parent model into the given child model. Implementations are expected to keep
     * parent and child completely decoupled by injecting deep copies of objects into the child rather than the original

import org.apache.maven.api.services.ModelProblemCollector;

/**
 * Handles injection of plugin management into the model.
 *
 */
public interface PluginManagementInjector {

    /**
     * Merges default values from the plugin management section of the given model into itself.
     *
     * @param model The model into which to merge the values specified by its plugin management section, must not be

                                } catch (InterruptedException ie) {
                                    // ignore
                                }
                                file.delete(); // if this fails, forget about it
                            }
                        }
                    } catch (TransferFailedException e) {
                        getLogger()

 * representation for models that physically look different but are semantically equivalent.
 *
 */
public interface ModelNormalizer {

    /**
     * Merges duplicate elements like multiple declarations of the same build plugin in the specified model.
     *
     * @param model The model whose duplicate elements should be merged, must not be {@code null}.

                try {
                    Thread.sleep(10);
                } catch (InterruptedException e) {
                    // ignore
                }
                metadataFile.delete(); // if this fails, forget about it, we'll try to overwrite it anyway so no need
                // to delete on exit
            }
        } else if (metadataFile.exists()) {

When deploying applications you will probably want to have some **replication of processes** to take advantage of **multiple cores** and to be able to handle more requests.

As you saw in the previous chapter about [Deployment Concepts](concepts.md){.internal-link target=_blank}, there are multiple strategies you can use.

process** (e.g. a Uvicorn process running your FastAPI application). They would all be **identical containers**, running the same thing, but each with its own process, memory, etc. That way you would take advantage of **parallelization** in **different cores** of the CPU, or even in **different machines**.

And the distributed container system with the **load balancer** would **distribute the requests** to each one of the containers with your app **in turns**. So, each request could be handled...