https://layer5io.github.io/exoscale-academy/pr-preview/pr-393/learning-paths/1e2a8e46-937c-47ea-ab43-5716e3bcab2e/certifiedcontainerengineer/Recent content in Certified Container Engineer on Exoscale AcademyHugoenhttps://layer5io.github.io/exoscale-academy/pr-preview/pr-393/learning-paths/1e2a8e46-937c-47ea-ab43-5716e3bcab2e/certifiedcontainerengineer/certified-container-engineer/Mon, 01 Jan 0001 00:00:00 +0000https://layer5io.github.io/exoscale-academy/pr-preview/pr-393/learning-paths/1e2a8e46-937c-47ea-ab43-5716e3bcab2e/certifiedcontainerengineer/certified-container-engineer/<h2 id="container" class="heading-link"> Container <a href="#container" class="heading-anchor" aria-label="Permalink to this heading">🔗</a> </h2> <h3 id="application-deployment" class="heading-link"> Application Deployment <a href="#application-deployment" class="heading-anchor" aria-label="Permalink to this heading">🔗</a> </h3> <p>Observing the evolution of application deployment highlights the advantages that containers offer.</p> <h4 id="traditional-deployment" class="heading-link"> Traditional Deployment <a href="#traditional-deployment" class="heading-anchor" aria-label="Permalink to this heading">🔗</a> </h4> <p>Initially, organizations ran applications directly on physical servers, lacking resource boundaries between applications. This often led to resource contention and underperformance. Running each application on its own server solved this but resulted in underutilized resources and high costs.</p>