Deploying Large-scale PHP


Comments are closed.

Colin O'Dell at 16:14 on 26 May 2016

This was an interesting look into how a major web company is able to release changes without downtime.

While the presentation did contain some interesting and useful tips, I felt it was a little too high-level and low energy. I also wish the presenters could've used the extra time to show some specific examples of the scripts, configurations, etc. to understand what I'd need to do to implement something similar.

Good overview of simplest way to push to production servers and on up to how deploys changes across servers. Not any details on how to get started with any of the tools they use because each tool could have had its own talk, but enough to research key tools mentioned. Were able to answer a lot of questions afterwards.

I liked the talk. What I think surprised me the most was the fact that deployments are made, live, during what are likely the heaviest periods of the day. The reason, of course, is that this provides a comparative basis against which to first judge the slow roll out before proceeding with the full. And emphasizes even more the importance of logging and associated dash boards. High level perhaps, yes, but for me, excellent. Thanks.

Zachary May at 11:13 on 27 May 2016

Two speakers was a bit awkward. Lots of unexplained acronyms and jargon.

The material was really specific to their use case and yet still not concrete enough. I do think it's valuable to just see what other organizations are doing, so that's perhaps a minor complaint.

Squirrel Nuts at 14:21 on 27 May 2016

Talk was a bit awkward. It was two engineers who didn't really explain who they were or what they did at Yahoo and probably hadn't given a talk before. But, agree with other commenters, it was interesting to here about what such a big PHP shop was doing to release code without any downtime.

Squirrel Nuts at 14:34 on 27 May 2016

Forgot to add... the conversation after the "talk" was actually better than the presetation. Might just do this as a open spaces thing if it is going to be part of the conference in the future.