Case studies
We describe specific deliveries: a database, a copy, the cloud and cost. Client names stay with us. The scope and the result are in the text.
A 1 TB copy and a restore that took several days
The copy was 1 TB. After an outage the team restored the whole disk, while the service only needed a few files to run. Transfer, verification and bringing the machine up took several days. In this case study we describe how we split a start restore from the full image, so the service returns to traffic without waiting for the whole set.
Read the case study
A production database in a container without a persistent volume
The production database ran in a container. A restart, a node drain or a new image left an empty data directory. The application came up. The data did not. In this case study we show why database state cannot live in the image writable layer, and how we arranged a volume, a copy and a restore exercise.
Read the case study
AWS without a landing zone and without cost control
The AWS account grew without a landing zone, without a list of instance types and without a cost trail during the week. The bill arrived only with the invoice, at the end of the month. In this case study we describe how daily reports, threshold alerts and instance-type order went in, and what that did to the bill.
Read the case studyWe will discuss operations or an audit
We will discuss infrastructure, risk and cost. On that basis we will prepare a scope of work.
Write to us