The Disciplines Plate V Cloud Infrastructure
Cloud
Infrastructure.
Set up and written down. Hosting, architecture and uptime for people who'd rather not learn Terraform.
Servers and cloud accounts set up carefully, monitored and handed over with runbooks written in plain English. Whether it is IONOS, AWS, DigitalOcean or Hetzner, I do not have a favourite and I will recommend whichever suits the job.
Return to the workshopA website or an application is only as good as the server it runs on. When that server goes down it costs you money, and if you look after it yourself it takes time away from the work you are actually good at.
I design, build and look after cloud infrastructure which stays up and grows when you need it to. I stick to open standards, and when it matters where the data lives I use EU hosting. You are never locked in, because the keys are yours and anyone can follow the runbooks.
§ What I provide
-
I.
Managed hosting
Web, application and database servers looked after for you, which means setup, security patches, backups, monitoring and maintenance. It runs on whichever provider you are already paying, or on a new one if that turns out to be cheaper.
-
II.
24/7 monitoring
Uptime, performance, disk space and security are checked around the clock, and the alert comes to me before you notice that anything is wrong, with automated checks and live dashboards behind it.
-
III.
Security hardening
Servers locked down from the first day, with firewalls, SSL certificates, automatic security updates, intrusion detection and regular audits.
-
IV.
Automated backups
Databases, files and configuration are backed up every day, stored offsite and tested regularly, and the recovery steps are written down. I have had to restore from them before, and it worked.
-
V.
Performance optimisation
Server settings tuned, caching in place, a CDN where it helps and the slow database queries fixed. The pages load faster, and a well-tuned server often needs only a smaller plan.
-
VI.
Scalability
You start small and grow when you need to, either with a bigger server or with more of them, and a busy day should not take the site down.
§ Typical architecture
-
Layer 1
Web server
NGINX or Apache, tuned for speed, with SSL/TLS from Let's Encrypt or a commercial certificate, HTTP/2, security headers and DDoS protection.
-
Layer 2
Application layer
Your application runs in its own isolated environment, whether it is Node.js, Python, PHP or something else. It restarts itself if it falls over, and resource limits stop it from taking the server down with it.
-
Layer 3
Database
PostgreSQL, MySQL or MongoDB, tuned for your data, with sensible indexes, backups, and replication if you need it. Slow queries are logged so they can be fixed.
-
Layer 4
Monitoring
Uptime checked every 60 seconds, plus performance metrics, collected logs and alert rules, using open-source tools such as Uptime Kuma, Prometheus and Grafana.
-
Layer 5
Backups
Automatic daily backups, stored offsite and kept for at least 30 days. I test restores, and the recovery steps are written down.
Questions, answered
Will we be locked into a particular cloud?
Not unless there is a reason for it. By default I use ordinary, portable technology which will run in more than one place, because the cost of moving later is the thing nobody prices in at the start.
What happens after it is set up?
You get runbooks written for whoever is on duty at the time, so that they make sense to someone who did not build it. Ongoing support is there if you want it, but the handover is written so that you do not have to take it.
What will it cost?
The prices on this page are starting points, so that you can tell in a minute whether you are in the right range. I then quote each job once we have talked it through, because the price depends on the shape of the job, and at this point nobody knows that yet. The first half hour is free, and usually it settles whether this is a small piece of work or a large one before any money is discussed.
Who owns the code when it is finished?
You do, outright, including the source. I hand it over with the runbooks you need to keep it running, and there is no licence to renew and no seat to pay for. Where this page quotes a monthly figure, that is for hosting or ongoing support, which is optional and can be stopped without taking anything away from you. When I say commissions, not subscriptions, I mean it literally.
What happens if you are unavailable?
I build everything so that somebody else could pick it up: common technologies, readable code, written runbooks and nothing proprietary. It is a fair question to ask of a one-person business, and the answer lies in how the work is built.
Do you work outside Suffolk and Cambridgeshire?
Yes. With local work you get the option of having me in the room, which is worth more than it sounds for the first conversation and for the handover, and for most clients everything after that is done remotely anyway.