Infrastructure · application implementation

Docker — containerising applications and environments

We prepare applications to run in containers and organise their deployment process. Docker and Compose help reproduce environments, while clear rules for data, configuration and updates make them easier to maintain.

02

Docker Compose

Services, networks, volumes and environment configuration.

01Images and relationships

Containerization of PHP, .NET, Python and Node.js applications

We prepare the Dockerfile and how to build the image with the proper runtime and dependencies. We separate the build and run steps when it helps reduce the content of the image. We select the process user and the scope of permissions required by the application.

The image has a reproducible version and a controlled update cycle. We do not include secrets and private files in the image. Updating Linux on a host does not automatically update the runtime inside a previously built container.

02Compose and networks

Docker Compose: application, database and workers

Compose describes related services, networks, volumes, and configuration. We separate the application, processes performing tasks and the necessary data services. We only list ports required by users or administrators; the remaining communication can operate on the internal network.

Development and production setups have different needs. In production, we select resource limits, logs, startup method and readiness control. Just starting a container does not prove that the database is ready or that the application can handle the operation.

03Volumes, backups and secrets

Container data, backups and confidential configuration

We keep persistent data outside an individual container's writable layer, for example in volumes or an external service. A volume survives container replacement, but is not a backup. We back up the database using a method supported by its engine to obtain a consistent recovery point.

We define how configuration and secrets are supplied at startup, including their permissions and rotation. A Compose secret supplied from a file does not automatically become an encrypted vault. Configuration backups also need protection and access controls.

04CI/CD and updates

Container implementations, monitoring and the possibility of return

The implementation process may include testing, building an image, checking dependencies, publishing in a selected registry and running a specific version on the server. We tailor CI/CD automation to the project and the level of control over changes.

We check the application status after implementation, access to the database and background tasks. The rollback plan takes into account data migration compatibility with the older version of the code. Restarting an old image does not itself reverse changes to the database. Logs, metrics and alarms cover the application and the host.

05Compose or Kubernetes

Compose, Kubernetes, and the limits of high availability

Docker Compose can support production deployment on a single host. It is a sensible variant when such an architecture meets the process requirements. However, restarting the container does not ensure operation during a server failure.

We consider Kubernetes when multiple hosts and services need orchestration and a team can maintain the platform. It adds management capabilities, but also cost and complexity. High availability still requires careful application, data, network and recovery design.

Compose and Kubernetes - scope of orchestration
SolutionScope and applicationWhat you need to remember
Docker ComposeDescription and launch of a set of services, often on a single server.Backups, host availability, updates and recovery planning are a separate scope of work.
KubernetesService orchestration in a cluster, deployments and mechanisms for recovering instances.Maintaining cluster, network and data and application readiness for this architecture.
Managed platformPart of the infrastructure or orchestration run by a vendor.Limits of liability, application portability, limits and cost of services.

Questions and answers

Before making a decision

Does Docker replace a virtual machine?

A container and a virtual machine provide a different type of isolation. Containers on Linux share the host kernel. They can be run on a VPS, virtual machine or dedicated server.

Does Docker volume protect against data loss?

A volume separates data from the container's lifecycle, but does not by itself protect against host failure, application errors or data deletion. Separate backups and a restore test are required.

Does every application need Kubernetes?

NO. For many implementations, a single host and Compose or another platform will suffice. Kubernetes makes sense when its capabilities match the requirements and there is a plan for maintaining the cluster.

Is it possible to move a ready-made application to containers?

Yes, after analyzing dependencies, files, application status, licenses and external services. Some components may remain outside containers if this facilitates consistent and predictable maintenance.

Let’s start with a conversation

What should become simpler in the next implementation?

Describe the application, dependencies, database, and current method of publishing changes. We will establish container boundaries, data storage and the update process.

Plan for containerization