Comments on: The Many Other High Costs Cloud Users Pay

By: Timothy Prickett Morgan

Timothy Prickett Morgan — Mon, 28 Jun 2021 17:47:23 +0000

In reply to Roy. My point is, don't overpay for that by 3X or 4X and then complain you can't pay for good programmers.

By: Timothy Prickett Morgan

Timothy Prickett Morgan — Mon, 28 Jun 2021 17:46:37 +0000

In reply to Alan Sill. I understand. They are proprietary clouds, aren't they?

By: Alan Sill

Alan Sill — Mon, 28 Jun 2021 06:45:32 +0000

Agreed on all counts, with one important terminology adjustment request: please stop using the misleading, incorrect, and technically subversive (in a not-good way) term “public cloud”. There are no such things as public clouds, not in the US anyway, except for small research shared infrastructures that I have spent a career trying to support and expand. What we have now in the US are commercial cloud service providers, and the correct and best way to refer to these right now is as what they are: commercial clouds. I’m on a campaign to stamp out the use of the term “public cloud” in favor of “commercial cloud” and request your cooperation in this.

By: Marco B.

Marco B. — Sun, 27 Jun 2021 04:49:58 +0000

Please give me advice on how a single senior level engineer or team manager in a global corporation could do something useful to get the attention of the corporate leaders to see what you are teaching to us in this article? Many of us on the battlefield intuitively know that what you are saying (and much of what was presented in the article you cited by Martin Casado) is true (the cost going up as the organizations grows, the loss of talent, the lack of control of our own technological destiny – not to mention the security of our information and intellectual property, etc.) but we are not necessarily part of those C-Class meetings where the decisions are being made. I love the company I work for and I fear that we may be heading down the path that ends up being one-way. Thank you for the article – I very much enjoyed reading it.

By: Roy

Roy — Sat, 26 Jun 2021 18:31:03 +0000

No one ever said not to own your destiny. Have your team, have your code for the apps that drive your business.
Still, operate at the *right* level of complexity.
When do you consider you have enough control of the stack? The server level? What about the OS? BIOS maybe? Or the electronics of the logic gates?

At the end of the day we all have limited resources and time. I would devote as much of my management attention to the higher stacks that actually touch/drive my business.

By: Timothy Prickett Morgan

Timothy Prickett Morgan — Sat, 26 Jun 2021 01:51:09 +0000

In reply to Joe Kesselman. They did not. But I certainly suggested that having cloud-priced OEM gear plus co-lo was better than building and depreciating datacenters for base capacity and then cloud for research, test, dev, and burst capacity.

By: Joe K.

Joe K. — Sat, 26 Jun 2021 01:50:03 +0000

(transient, not transit, of course. Darned auto incorrect…)

By: Joe Kesselman

Joe Kesselman — Sat, 26 Jun 2021 01:48:40 +0000

It would be helpful to have a discussion if how hybrid cloud fits in this analysis. On the face of it, that would seem to be the easiest way to take something grown in/for the cloud back onto company owned and managed compute resources, while retaining the cloud model’s advantages in handling rapid/transit scaling changes. Yet it seems that was not discussed. Did I miss something, or did the authors of the paper and article?

By: F

Fri, 25 Jun 2021 16:16:56 +0000

Excellent perspective. I very much enjoy your keen insights into the next 3-5 years of the computing landscape.