4 ms·
I think this is a common need, even in smaller organizations. Spinning up/down deployments doesn't imply you're doing it in response to scale needs (most orgs d
by zbentley 5y ago
I think this is a common need, even in smaller organizations. Spinning up/down deployments doesn't imply you're doing it in response to scale needs (most orgs don't have those); often it means you're simply experimenting with new tools or new product offerings. Having the ability to do that without waiting for infrastructure provisioning, and having the ability to only spin up the resources you need to see (for example) if a given version of a web framework can run your site well, or of a new database meets your needs, can be a significant value add.
- AnIdiotOnTheNet 5y ago> often it means you're simply experimenting with new tools or new product offerings. That only makes sense to me in the context of a business being an IT shop to begin with. Most businesses aren't, and their new product offerings require factories and dies and labor and materials. Besides which, the problem of provisioning is entirely overblown for this scale of business. I can spin up new servers all day on our on-prem vSphere cluster.
- dagw 5y agosense to me in the context of a business being an IT shop to begin with. Lots of businesses outside of 'IT shops' use computers. I currently work in Civil Engineering and more and more of our product and service offerings have an IT/Online/Web based component which involves setting up some sort server. I can spin up new servers all day on our on-prem vSphere cluster. I what price? At my old job an on-perm vSphere 'machine' cost my department a lot more than what AWS was charging.
- AnIdiotOnTheNet 5y agoWe've had the same vSphere cluster for 5 years now. I forget what it initially cost, but over the timespan in question I think it would be very difficult for Cloud-anything to cost less. Hell, the licensing for the software we use to do business costs an order of magnitude more.