3 ms·
> And you will be doing so in an exact replica of the machine, minimizing the bugs or issues introduced when an staging or test system had changes applied. Ano
by r00fus 15y ago
> And you will be doing so in an exact replica of the machine, minimizing the bugs or issues introduced when an staging or test system had changes applied. Another one: it is simple to resize your server as needed. You can start with a micro instance when developing and then scale to bigger instance types as needed after you on production
VMware? Assuming you are limited to on-premise options, isn't this kind of flexibility addressed with in-house virtualized instances? At a previous employer (who was too paranoid about cloud) I could easily pull a snapshot of prod into a test/dev environment with a few clicks and coffee-break worth of lagtime (likely possible with command line too), then use my deployment process to push changed code/metadata changes back out to prod if need be.
The only downside to this approach is you need to have IT ops that's up to snuff on virtualization (not guaranteed)... with cloud you cut this out, and your devops guy can manage everything.
- ridruejo 15y agoYes, I was referring to 'traditional' hosting. The VMWare vcloud offering is actually quite interesting in the ease with which you can migrate from on premise to public vcloud providers. Still way more expensive that just going the Amazon route for most people