Discipline 04

Infrastructure & DevOps Engineering

We build and maintain the infrastructure that keeps digital services dependable.

The challenge

What this discipline addresses.

Software is only as dependable as the infrastructure beneath it. Untested backups, manually configured servers and undocumented deployments are all sources of avoidable downtime. We make infrastructure repeatable, monitored and recoverable.

  • Manual releases introduce risk with every deployment.
  • Backups exist, but restoration has never been tested.
  • Knowledge of the server configuration rests with one person.
  • Outages are reported by customers before they are detected internally.
  • Hosting costs and capacity are not aligned with actual usage.
Services

What we deliver.

  • Linux server administration
  • Infrastructure management
  • DevOps implementation
  • CI/CD pipelines
  • Server configuration
  • Networking and connectivity
  • Backup and disaster recovery
  • Hosting architecture
  • Infrastructure monitoring
SourceCI checksReleaseProductionBackupsMonitoringRestore test
Reference architecture, for illustration.
Engineering approach

How we do it.

  1. Document what exists

    We record the current environment, its dependencies and its single points of failure.

  2. Make it repeatable

    Configuration and releases become scripted steps rather than individual memory.

  3. Prove recovery

    Backups are restored in a test, and recovery time is measured rather than assumed.

  4. Watch it

    Monitoring and alerts tell you about a problem before your users do.

Typical engagements

Where we usually start.

  • Moving an application from a shared host to a properly managed server.
  • Adding automated checks and repeatable deployments to a manual release.
  • Testing and documenting a disaster recovery plan.
Questions

Frequently asked.

Do we need the cloud?

Not always. The right hosting depends on data location, budget, connectivity and in-house skills. Some of the systems we work on are designed to run offline on site.

Can you manage infrastructure we already have?

Yes. We begin by documenting it, then agree what we take responsibility for.

How often should backups be tested?

On a set schedule, and always after a significant change. An untested backup is an assumption.

Discuss your infrastructure & devops requirement.

Describe the requirement and the constraints you are working within. We will assess it and advise candidly on whether and how we can help.

Discuss a Project