Blood, Sweat & Kubernetes at Laravel Hungary
I gave my first talk as part of the Laravel team at the Laravel Hungary meetup in Budapest. Here is the recording and some takeaways from presenting Laravel Cloud infrastructure to the Hungarian community.
I've been touring "Blood, Sweat & Kubernetes: A Laravel Cloud Story" across meetups. I first gave it at the Laravel Copenhagen Meetup at Luxplus in January, then at Laravel Aarhus at Gejst studio in April, LaraFest in the Netherlands in May, and then flew to Budapest for the Laravel Hungary meetup. The Hungary edition was the first time a Laravel team member had spoken live at their meetup.
The talk
I walked through how Laravel Cloud uses Kubernetes-based infrastructure under the hood. How we actually manage containers, handle deployments, and what breaks when you run PHP at this scale. Kubernetes is powerful but unforgiving.
The recording is on YouTube:
Speaking as part of the Laravel team
This was my first conference-style talk since joining Laravel in October. I had done internal presentations, but standing in front of a community meetup and representing the team felt different. There's a weight to it. People come with real questions about Laravel Cloud, about infrastructure decisions, about what is coming next. Some of those I could answer. Some I couldn't.
The Hungarian community came prepared. The questions after the talk were technical and specific. People wanted to know about container orchestration details, PHP-FPM tuning in Kubernetes pods, and how we handle zero-downtime deployments. These are the conversations I enjoy most.
Budapest
Good venue, good pizza, and an audience that clearly builds real things.
Takeaways
Presenting infrastructure work to a Laravel audience is different from presenting it to a DevOps crowd. Laravel developers think about infrastructure through the lens of their applications. They want to know how it affects their deploy workflow, their queue processing, their response times.
I left Budapest with a list of questions I need better answers to.