3 ms·
>In the cloud, this exercise would likely cost me $$$ every month, since I'd have to keep around hundreds of GB of virtual volumes. Personally, I'd rather pay
by incision 13y ago
>In the cloud, this exercise would likely cost me $$$ every month, since I'd have to keep around hundreds of GB of virtual volumes.
Personally, I'd rather pay some cloud provider a few dozen dollars per month to hang on to a bunch of volumes and snapshots that I can access/redeploy trivially from anywhere than maintain all the same in my home.
- toyg 13y agoI guess I'm special: most of my engagements drop me on-site without real connectivity (even 3g is often poor). But yeah, I see your point. As a company, we're a bit behind on the whole AWS thing, mostly because of fear of ungodly bills at the end of the month. Funnily enough, I'm the only one here trying to actually use it.
- ckozlowski 13y agoI'm tempted to go this route in the future instead of the home ESXi server I run. I realize this is probably a bit unique compared to most, but a lot of what I do in my instance is build private clouds for customers. AWS is great, but their infrastructure is already built; its the end stage at which most of the heavy lifting has already been done. The deployments are automated and the work has been done for you already. This is great is you're a developer and you don't have time to worry about all of the backend nonsense, you need an infrastructure and you need to start on your application/web frontend/whatever right now. Regardless of where you're hosting it though, losing access to the MS library is going to be a heavy blow.