Cloud Infrastructure & DevOps

Good infrastructure is boring: every merge deploys, servers come back after a restart, and you hear about problems before your customers do. I set up that kind of infrastructure for production applications.

I hold four AWS certifications: Solutions Architect – Associate, Developer – Associate, AI Practitioner and Cloud Practitioner. On AWS I work with EC2, S3, Lambda and RDS. Outside it, I deploy frontends on Vercel and run applications on VPS hosts with Docker, Nginx and Coolify.

Applications are containerised with Docker, so they run the same on a laptop and in production. CI/CD pipelines in GitHub Actions run the checks and deploy on every merge. Servers run Linux, configured and documented so your team can look after them.

Infrastructure should fit the budget too. On PitchPool, consolidating background jobs cut idle database traffic by around 90%, which let serverless PostgreSQL scale to zero when nobody was using it.

Databases are deployed alongside the application, and monitoring is in place before launch rather than after the first outage.