Cloud operations: lessons that connect
Different projects, the same habit: reduce bottlenecks, detect trouble early and make infrastructure easier to change.
For confidentiality reasons, I can’t describe specific projects from my work for employers in detail. This also means I can’t showcase the complex real-world applications developed in those projects here.
4 project stories · 3 technical notes
How do you absorb a traffic spike?
Taking static delivery off the web servers
Project period: 2008
Read the project story ↗02How do you hear about trouble first?
Before the customer becomes the monitoring system
When I joined in 2000, a handful of servers and log-analysis scripts were enough to describe the starting point—not a monitoring system that could keep up with growing complexity.
Read the project story ↗03What if the original design does not work?
From bare metal to VMware
Started June 2011
Read the project story ↗04How do you make the next change easier?
Cloud-native portfolio platform
A legacy WordPress site became a fast, static AWS platform with a smaller attack surface, automated delivery, and transparent visitor analytics.
Read the project story ↗From the story to the technical detail.
Existing Notes articles, collected here so you can follow a topic without searching the archive.
The Six-Month Time Bomb: When EFS Ran Out of Burst Credits
How an Amazon EFS burst-credit balance concealed an unsustainable storage workload for six months—and the monitoring lessons learned.
Read the technical note ↗How to Monitor EFS Burst Credits with CloudWatch
A practical CloudWatch monitoring design for EFS throughput, burst-credit depletion, I/O pressure and application impact.
Read the technical note ↗AWS Autoscaling / ELB Health Checks
Here is a tiny yet very important hint, if you deal with let's say an ALB and Autoscaling groups in AWS. By default ASG use EC2 as their health check. That me
Read the technical note ↗

cloud / systems