One of the pervasive properties of software is change. \u00a0Whether this change comes from regular enhancements or environmental updates, it is one that should be considered strategically for production software. \u00a0Thus, the balance of upgrades vs. stability needs to be considered as your solution ages.<\/p>\n
Modern software environments provide features that make upgrades easier than in the past. \u00a0A great example of this is WordPress and other “plugins supported” solutions. \u00a0The goal is to make administration of these sites easy and quick. \u00a0Thus, you often can upgrade a plugin or even the core software to the latest version with the click of a button.<\/p>\n
This ease extends to core environments as well. \u00a0There are a lot of automated update\u00a0tools available to keep all of your software up to date. \u00a0The most well known of these is the windows update tool provided in many recent Windows OS versions.<\/p>\n
This ease of administration is excellent. \u00a0However, it is also hazardous. \u00a0An upgrade may break your entire site and lose sales. \u00a0As scary as that sounds, even worse side effects can happen. \u00a0Data may get corrupted, backups can become invalid, and fulfillment can be sent to the wrong address. \u00a0These worst-case scenarios are not exactly typical, but they can happen. \u00a0Upgrading your system can turn a steady running and reliable system into a nightmare.<\/p>\n
These concrete impacts are just one facet of the considerations. \u00a0Updates may change the user experience. \u00a0Something as trivial as moving a menu item can cause user headaches and negative backlash. \u00a0For some great examples of this, look at some of the Facebook changes over the years that caused a massive outcry from their user base.<\/p>\n
It may seem that these risks point to leaving your software in its original state as long as possible. \u00a0Fewer changes should lead to higher stability. \u00a0This is only partially true. \u00a0A stable system is more accessible to hack and may be steadily approaching a point of no return. \u00a0In the latter case, this can be a point where the system lacks the resources to support the user base or amounts of data within the system.<\/p>\n
There are also license considerations and support. \u00a0Older software may not be supported by vendors entirely or at all. \u00a0Thus, we need to find that balance. \u00a0Here are some high-level steps that can be taken to keep your solution\u00a0up to date while minimizing risk.<\/p>\n
Vendors do not release updates on the same schedule. \u00a0However, you can set a timetable for when you will apply updates so you can keep those updates on a plan suitable to your business. \u00a0I recommend updates on a frequency of two to four times a year.<\/p>\n
It is recommended that you have multiple environments during implementation. \u00a0This is even more important once you “go live.” \u00a0The value of these other environments is that they allow you to create an identical version of your production system for testing. \u00a0Thus, nearly all of the risk can be assumed by a “test” environment instead of production. \u00a0This is not a silver bullet, but it is pretty darn close.<\/p>\n
Before any update is made, make sure the whole system is backed up. \u00a0This will allow for roll-back in case an update is not viable.<\/p>\n
When you follow the suggestions above, it should help you buy some time before implementing an update. \u00a0This should be embraced and used to allow you to pass the\u00a0risk on to other customers. \u00a0They can perform the update, and their feedback will help you avoid problems and reduce risk. \u00a0In effect, waiting on an update allows others to be your guinea pig.<\/p>\n
These are general suggestions, but embracing them can be very useful. \u00a0There is always going to be a challenge in finding the balance of upgrades vs. stability, but when you reduce risk, it makes success more likely. \u00a0Following the steps noted here can provide a win-win situation where you have current software and a stable experience for your customers.<\/p>\n","protected":false},"excerpt":{"rendered":"
One of the pervasive properties of software is change. \u00a0Whether this change comes from regular enhancements or environmental updates, it is one that should be considered strategically for production software. \u00a0Thus, the balance of upgrades vs. stability needs to be considered as your solution ages. Easy Upgrades Modern software environments provide features that make upgrades […]<\/p>\n","protected":false},"author":1,"featured_media":302,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[20],"tags":[25,11,26],"class_list":["post-301","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-building-software","tag-maintaining-software","tag-security","tag-stability"],"yoast_head":"\n