A few years ago, software releases were all scheduled. Any change to that schedule, and it was pure and utter chaos. In between the software releases, the maintenance team would take over to ensure that everything ran smoothly until the next update happened. It was all very quaint, and an outmoded model for software infrastructure. Nowhere is this truer than on WordPress (WP) sites. Because of the constant nature of the updates to the platform, along with all of the plugins and themes, it shifted how developers work with the update model. The biggest change is the rise of the Developer Operations (DevOps) model. Since the advent of Developer Operations the idea of periodic updates has been thrown on its head. Instead of regularly scheduled updates, developers and IT operations merge together to constantly update systems as needed. 25% of the top million websites now run on WordPress, as adoption grows, especially in the Enterprise, DevOps for WordPress is going to become a must. What is DevOps for a WordPress Infrastructure The term DevOps is so new that it is still being defined. However, the most common definition is “Continuous improvement, feature releases and updating of an app
Share This