Manage demand and supply resources
| CONTAINER_BUILD_COST_07: How do you minimize cost for your containerized application during startup time? |
|---|
Longer startup times for containerized applications can result in wasted compute resources.
Shortening startup times can be done on the application-level (code optimization), or on the container level. For example, if the application needs external dependencies to be present in the container, it should be already installed during the build process, or it should be included in the parent image, and not downloaded at startup using an entrypoint script or DOCKERFILE commands.
| CONTAINER_BUILD_COST_08: What systems are you using to create your container build process? |
|---|
Creating any build process requires developing, maintaining, and operating a build system. This can be done by a variety of methods, such as using OSS tooling for job automation, or using self-developed systems that are able to run build scripts for your application. However, running and maintaining this kind of system involves software development costs, operational costs, compute, and storage costs for running the system. Alternatively you can use build and pipeline services, such as Amazon EC2 Image Builder, AWS CodeBuild, and AWS CodePipeline. Using managed services removes the operational overhead and allows developers to consume pipeline runs and build jobs on a pay-as-you-go basis.