Switched to a managed disk service after receiving frequent low disk space warnings from Prometheus due to its retention policy, trading off control over data storage for reliable alerting and automated cleanup mechanisms

Tunnel vision on Kubernetes led to overengineered solo operator infrastructure, neglecting simpler mechanisms like static site generation for low traffic websites

Using Nginx as a reverse proxy revealed single point of failure in my solo operator infrastructure when the server crashed due to high memory usage from Apache

Using Kubernetes for solo operator infrastructure often introduces unnecessary complexity when a simple Docker Compose setup is sufficient for small scale deployments with few services.

Monitoring tool alerted to a misconfigured firewall rule causing dropped packets on the solo operator infrastructure, added automated rule validation to prevent recurrence

I switched from NGINX to Lighttpd for my solo operator infrastructure. I was experiencing issues with server performance under heavy load, which led me to reevaluate my web server choice. Lighttpd is now in use for my infrastructure.

Using AWS Lambda as a solo operator infrastructure led to a mistake where incorrect IAM roles were assigned due to assuming a single role could handle multiple functions, resulting in restricted access to necessary resources.

Switched to a load balancer with automatic instance scaling to handle traffic spikes on the solo operator infrastructure, observed a decrease in 5xx errors from the nginx log output

Using AWS Lambda as a solo operator infrastructure led to cold start issues with Node.js runtime, causing inconsistent response times due to delayed function initialization. Next time would use provisioned concurrency to mitigate this.

Deployed a minimal DNS server using CoreDNS to handle solo operator infrastructure routing, encountered issues with zone file configuration that required manual editing to resolve.

Stripe webhooks trigger resend on retry states 4+ to ensure zerodowntime for transactional emails

Stripe webhooks on Fly.io require idempotency keys to prevent duplicate payments on retry states 4+