3 ms·

Also experience. My team has been doing cloud deployments for the last 18mths, now we are on a gig at a company that has onprem. In theory the onprem infrastruc

by sgt101 5y ago

Also experience. My team has been doing cloud deployments for the last 18mths, now we are on a gig at a company that has onprem. In theory the onprem infrastructure is comparable to cloud (K8's, GPU's, HDFS, Kafka) but the reality is that to get a set of K8's pods for a release has taken 2 weeks, 10+ meetings (calls) countless messages and 40+ emails. And the ones we got on Friday were wrong (we asked for 3 * 16GB ones + 1 * 2GB, we got a 16GB project container with 4GB pod limits). For our hadoop request - yes it got provisioned in >8hrs (mostly I think because no one is using it) but none of the access instructions work and everyone who has used it is mysteriously unavailable - so we can't access it. Compare and contrast to self service from any cloud. Why : well it's demand management. If you do self service and say "pay for what you want" then IT's costs bloom and the CIO is shot. If you do that in a cloud scenario then Cloud costs bloom and the CIO says "you guys have spent your money badly". This means that you need police and you need people who you ask to give you what you need if they are happy. These people obstruct you and then get things wrong.

mfer 5y ago
You bring up some great points. There are two that I see. First, there are internal processes. All too often they end up needlessly slowing velocity. This isn't a technology problem but a people problem. Using a public cloud enables people to circumvent these issues, in some cases. Second, there are costs. What does it cost to give someone the features they ask for in the time they want it? This is a requirements, design, time, and cost problem.
- sgt101 5y ago
  Yes - thinking about it, it's a market failure. Basically small markets (internal IT) can't sustain the investment to support the requirements design time cost issue - while the public cloud folk can say "any colour you like so long as it's black" and there are enough takers to pay for it all.

by sgt101 5y ago

mfer 5y ago

You bring up some great points. There are two that I see. First, there are internal processes. All too often they end up needlessly slowing velocity. This isn't a technology problem but a people problem. Using a public cloud enables people to circumvent these issues, in some cases. Second, there are costs. What does it cost to give someone the features they ask for in the time they want it? This is a requirements, design, time, and cost problem.

sgt101 5y ago
Yes - thinking about it, it's a market failure. Basically small markets (internal IT) can't sustain the investment to support the requirements design time cost issue - while the public cloud folk can say "any colour you like so long as it's black" and there are enough takers to pay for it all.