The outage of the WordPress keeps getting attention, and this could be understood. Some people argue that a feathered approach to rollout is probably not so bad idea. They suggest not to deploy a code change to all the hotels while rolling out, notwithstanding of how well-tested it is. That’s how a feathered release cycle works: it delivers the code change to just one hotel in one go, and then waits some time to ascertain that nothing disastrous has happened. It can be amazing what a difference a single day can make in apprehension of the prospective pitfalls of this new release. If you have the operational flexibility to run multiple hotels, then you are able to adopt all kinds of release feathering techniques. When choosing whom to start with, opt for smaller clients, brand new clients, freemium clients, and beta testing clients, as it can lead to considerable risk relaxation for most of your clients.
The others suggest that multi-tenant architectures should learn how to push customers to new releases. Actually, not every release is always so over-arching that everybody has to immediately go there. Maybe some of them could be voluntary to make people able to do the same as what you offer but without the hosting.
As the conventional SaaS has only got one code line, there can be serious troubles with it if users don’t move forward quick enough. That’s why there’s a suggestion to set up a window during which the user has leeway to select the migration point. For example, if you release quarterly, probably the window is the first 3 weeks afterwards is available.
Every significant website – Freshbooks, Google, NetSuite, Salesforce.com and many others have had that unscheduled downtime experience, and it actually has been a matter of how you negotiate and manage it. However, there isn’t any recorded file of business critical data lost so far.
As programs are getting more complex, the probability of an outage or serious bug rises. Everyone knows about patch releases, as well as about the fact that users are usually tending to a connected world where all the systems around the world present actual information and it isn’t hard to find out how one faulty service could influence others.
Like all emerging markets, here things change as well, and a WordPress outage of the scale might finally be a good factor.
Post Tags: blog failure, blog news, wordpress failure, wordpress news, wordpress security
