BVCC-Holding
Worked on the servers, cloud environment built, applications containerised, operation and scaling orchestrated.
- A direct line to your engineer
- Operation including hardware replacement
- Planned and built for your business
Who operates the servers and cloud services of BVCC Holding?
NDVDL. The BVCC Holding group needs reliable operation of its servers and cloud services without keeping infrastructure of its own on site. NDVDL works on the group's servers, built the cloud environment on AWS, packaged the applications into Docker containers and set up Kubernetes to orchestrate operation and scaling. The infrastructure itself is defined as code with Terraform rather than configured by hand. Hosting and ongoing operations also sit with NDVDL — the contribution therefore ranges from the servers through the cloud environment to permanent care.
Our role at BVCC Holding
BVCC Holding is a group of companies whose services have to keep running without operating a data centre of their own. NDVDL works on this group's servers: setup, operation and maintenance sit with us.
Beyond that we are responsible for the cloud environment the services run in — built on AWS, containerised with Docker, orchestrated through Kubernetes and captured as code with Terraform. Hosting and ongoing operations are part of it: monitoring, updates and scaling stay our job, not the group's.
Starting point
The BVCC Holding group needed reliable operation of its servers and cloud services without keeping infrastructure of its own on site. NDVDL works on the servers and takes care of hosting and ongoing operations.
What we did
Work on the servers
Setup, operation and maintenance of the group's servers.
Cloud infrastructure on AWS
Building the cloud environment on AWS for hosting and operating the services.
Containerization with Docker
Packaging the applications into Docker containers for consistent operation.
Orchestration with Kubernetes
Operating and scaling the container landscape with Kubernetes.
Infrastructure as code with Terraform
Documented, reproducible infrastructure instead of manual, one-off steps.
The technical details are project-specific — we're happy to walk through the exact implementation in person.
From analysis to day-to-day operation
No off-the-shelf project — a clear path to IT you can rely on.
- 01
Initial Consultation & Analysis
We take a look at your IT — free of charge and with no obligation. You get an honest assessment: what's good, what's missing, what's risky.
- 02
Concept & Offer
You receive a concept tailored precisely to your business — explained in plain language, without jargon and without hidden line items.
- 03
Implementation
We build your infrastructure — cleanly documented and with minimal disruption to your day-to-day operations.
- 04
Operation & Full Service
After installation is when we really get started: monitoring, maintenance, optimization — and hardware replacement when something fails, if you want it.
Technologies used
Servers
The machines the group's services run on.
Servers are the part of IT nobody notices as long as they run — and that brings everything to a halt when they fail. Setup, updates, monitoring and maintenance therefore belong in dedicated hands instead of being a side task for someone whose actual job is something else.
AWS
Cloud platform where the services are hosted and run.
Since BVCC Holding doesn't keep its own on-site infrastructure, a cloud platform has to provide compute, network, and storage instead. AWS supplies those building blocks without physical servers having to be procured or operated.
Docker
Packaging the applications into consistent, portable containers.
A container bundles the application together with its dependencies in a fixed state, so it runs the same way regardless of the underlying server environment. That reduces the differences between development and production environments that otherwise cause hard-to-reproduce bugs.
Kubernetes
Orchestrating and scaling the container landscape during ongoing operation.
Kubernetes automatically restarts failed containers and distributes them across available resources instead of that being watched manually. That matters particularly when a set of services needs to stay available continuously without each instance being managed individually.
Terraform
Describing the cloud infrastructure as code instead of manual configuration.
The infrastructure is captured in versioned configuration files rather than existing only as a click history in a web console. That makes changes traceable and the setup reproducible when needed.
What makes this technically demanding
Building containers with Docker is the easier part; keeping them reliably available during ongoing operation is what Kubernetes actually does. If a container fails, it has to be replaced automatically, and under changing load, additional instances have to be started or scaled back down without interrupting the running services.
Because NDVDL handles hosting and ongoing operation, the cloud infrastructure has to be maintainable and adjustable reliably, without being reconfigured from scratch for every change. Terraform captures the target state of the infrastructure in code, which makes adjustments traceable and repeatable instead of being made manually in the AWS console.
Technical questions about this project
Question not covered here?
Call us or send an email. You speak directly to an engineer — even if it never turns into a project.
Services this project demonstrates
For your business too: infrastructure that just works
Let's talk about your situation — no obligation, free of charge.