![]() The equations change as your business changes. Outside of the extreme cases, having some wild guess of "how much does an environment build cost", "how much does this bug cost per day", and "how much does it cost for a client to be down" can greatly improve your choice of tradeoffs. You choose "fix it in x.z" because that's the obvious answer. If you cost of making an environment is high, e.g., mount a spare scratch-monkey or embed in a fresh aircraft carrier, then off course you won't. The cost is low and pays for the benefits. spinning up dozens of virtual machines from build scripts, then make them whenever needed. If your cost of making an environment is low, e.g. If it isn't a question about money, frame it terms of money anyway. But even if it's a known practice, I can't recommend this for critical systems, except in rare exceptions where there is no other alternative. In this case, an exception procedure could lead to a direct development (option 3). ![]() Last but not least, a risk assessment could consider that the patch is a minor change with no real risk. But if your company has a professional datacenter, they should be able to virtualize such an environment and restore older images very easily and without huge overhead costs. This approach is also the most expensive one. There, the clone acceptance is even created at the beginning of the upgrade, just in case of. This is the standard procedure for the upgrade of major ERP systems, when the whole company depends on the production environment. Therefore the safest approach is to go for option 1. Overriding acceptance could in this case lead to persistent inconsistencies. The showstopper is when there is a database, and different version might cope differently with the persistent data. This makes it risky to move back and forth. ![]() Unfortunately many complex business applications are more delicate to deploy: you may need to install a set of dependent dynamic libraries or plugins, or you might need to update some configuration files, etc. If deployment on acceptance is more delicate. redeploy (or rollback to) the current version under development.for example if you just have to replace the executables, you may consider option 2: If deployment on acceptance environment is easy. This all depends how easy it is to change the acceptance environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |