Does Cloud really save costs?

From Alex Xu

Letโ€™s look at this question ๐ข๐ง ๐š ๐ฅ๐จ๐ง๐ ๐ž๐ซ ๐ญ๐ข๐ฆ๐ž ๐ซ๐š๐ง๐ ๐ž to see what the cloud really brings us.

๐Ÿ”น When a company or a business line initially starts, product-market fit (PMF) is key. The cloud enables quick setup to run the system with minimal necessary hardware. The cost is also transparent.

For example, if we run the databases on-premise, we need to take care of hardware setup, operating system installation, DBMS maintenance, etc. But if we use Amazon RDS (Relational Database Service), we just need to take care of application optimization. This saves us the trouble of hiring Linux admins and DB admins.

Later, if the business model doesnโ€™t work, we can just stop using the services to save costs without thinking about how to deal with the hardware.

๐Ÿ”น In research conducted by Cameron Fisher, the cloud starts from ๐š๐ฅ๐ฆ๐จ๐ฌ๐ญ ๐ณ๐ž๐ซ๐จ ๐œ๐จ๐ฌ๐ญ. Over time, the cost starts to accumulate on subscriptions and deployment consulting. Ironically, because it is so easy to allocate services to the cloud for scalability or reliability reasons, an organization tends to ๐จ๐ฏ๐ž๐ซ๐ฎ๐ฌ๐ž the cloud after adopting the cloud. It is essential to set up a monitoring framework for cost transparency.

๐Ÿ‘‰ Over to you: Which notable companies use on-premise solutions and why?

Reference:

  1. AWS guide: Choosing between Amazon EC2 and Amazon RDS
  2. Cloud versus On-Premise Computing by Cameron Fisher, MIT


Comments:

This looks like it only accounts for infrastructure. 

What are the ongoing costs of:

- having to pay and run an operations team
- slower development => larger team or slower development
- higher downtime ( you can't expect to compete with AWS) 
- opportunity cost 

I also don't think you can do a reasonable comparison without attaching a scale of company to the equation. 

If you're a startup with 20 devs, even the added overheads of an ops team could ruin the books. 
"We saved 50% vs our $400k AWS bill by hiring a $300k ops team"

If you're the size of basecamp then the overheads of running your own hardware are dwarfed by the cost savings vs cloud. 
I am Cloud First and work almost exclusively on cloud applications (serverless first even, but not exclusive) my thoughts on this debate is anytime someone says it's one way or the other they are missing many key points and ignore situational context.

Some key points I look for:
Are they avoiding lift and shift?
Are they using cloud native?
Are they using managed services?
Are they using serverless?
Do they monitor and adjust provisioned resources?
When accounting for costs, do they include total cost of ownership (e.g. employee time)
Even if more expensive, does the freedom of clicking a few buttons to change hardware power meet their needs better?
What is the outlook 10 years from now for this?
What sort of on prem solutions would be the alternative and do they provide the robustness and uptime needed by the client?
How much money is lost by either waiting for hardware to be delivered and installed, or lost money per minute/hour/day of downtime?
What happens if there is turnover in the staff, can the new staff get up to speed quickly on either the on-prem solution or the cloud solution?

There's probably more, but depending on many of these answers the move to cloud could be worth it or it could be a complete disaster.
For longer run you can get into 3yr-5yr contract where cost will reduce down to as low 50%.

Besides this after 5 yrs your on-premise hardware might become obsolete and then you again have to reinvest in capex to buy all of them.

But in cloud you can easily replace old hardware with the new as you are still on rental basis.

There are other factors like dynamic requirements, scalability, flexibility all these can make big difference to the business which is not considered in the above graph.