Talk in English - UK at phpDay 2018
Short URL: https://joind.in/talk/a167f (QR-Code (opens in new window))
Developers of applications under continuous high load often struggle with delivering new features and improvements without taking the app offline, performing the required migrations and taking it back online. I will show battle-tested procedures how to perform migrations without any disruptions. To survive in a competitive market, a software team must be able to deploy new versions of their application as frequently as possible, delivering new features, improvements and bugfixes for their users and stakeholders. Deployments should not be limited to a certain time or to a certain number, otherwise they become a bottleneck for the development process. To avoid disruptions when frequently deploying new versions, developers must adopt a set of practices that allow changing the database schema in production without users even noticing. As a result, the development process becomes much more safe and smooth. I will also talk about zero downtime deployments. They are less about development practices and more about deployment automation and webserver configuration. Some tips might even make your application perform faster!
Comments are closed.
Speaker was a bit nervous and not looking too much to the croud, but otherwise fine. Content was not cutting-edge, but it covered a lot more deploy-related issues that I expected, which was very nice!
Clear and simple set of tricks and suggestions very useful.
Useful tricks on matters that are often less obvious than they should be
Good tricks I’ve never thought about. Maybe more rythm would have been better as from center part on I was struggling to follow with the concentration that this subject would have been deserved.
I’ll take home good advices btw
Real life examples
the talk was good but also obvious. It could be the right way to do migration but the effort to do it to expensive in term of time and costs
Very logical talk. Something was obvious, other things were kinda tricky instead.