There are many steps you can take before buying concrete to build a DC. Even before you have to buy your own rack.
But, uh, wasn't this about their current expenses? Or their expenses at some point after their AWS bill got bigger than 1-2 employees?
And even with current expenses, building out a core competency in infrastructure that has nothing to do with your domain of expertise can be a distraction.
If you can't find anyone to even handle the hiring, let me stay far away from this company that teeters the verge of collapse when someone gets sick.
In fact, I was offered a job as a “digital transformation consultant”/“enterprise architect” to be the face of a company that did just that - take over a complete project for funded startups or other companies who had an idea but no in house expertise. Of course I would be the face of the company where most of the work would be “rural sourced” and outsourced.
The alternative being that they should have build an expertise in using AWS instead?
I'm not particularly trying to argue either way; I'm just saying that claiming that using AWS doesn't need expertise is a false premise. AWS isn't special here, either.
If instead you use some sort of abstraction and/or tooling, now you need expertise in that tooling.
Uber's doing that and they're a comparable company.
Even Amazon uses their own separate, dedicated systems for a lot of stuff - not public AWS I heard.
Microsoft is the most valuable company in the world. When it comes to stock Facebook probably would be not in FANG anymore because of their drastic stock drop over last year.
There are dedicated REITs that hold only high-tech/data center real estate.
[1] https://www.fiercehealthcare.com/tech/lyft-announces-integra...
https://www.nytimes.com/2018/10/01/upshot/uber-lyft-and-the-...
https://slate.com/technology/2018/02/when-should-you-uber-to...
But yes, it was disturbing when Tesla was using Ubers for people who had exposed bone.
Providing transportation for patients is so that __people can get healthcare__! A hospital/HCSP not making a few hundred/thousand is completely insignificant when compared to the real problem: People can't get healthcare or can't get to it.
I just take issue with this viewpoint where the concern for the dollar is placed before people's needs.
On top of that you have to hire people to manage it.
I think they'd be much better off just renting some space out in a datacenter and run the show themselves!
* No, using a colo saves you way more than just 20%. In one of our facilities, our org has maybe ~15k servers under management and dc costs are ~ 1 million/mo. Build out of the cages and racks wasn't incredibly expensive, I think ~2 million. Power isn't insane either.
* I have no idea what he's talking about re: the fiber statement. We have a blend of different backbone providers that give us ~100 gigabit for ~$0.60 per gig. Compared to bandwidth costs for AWS, it's dirt cheap.
* You don't need ultra fast hot swappable robotic arms if you're not FAANG. With a handful of dc techs and a simple monitoring system, you can swap out disks just as easily, at the expense of a little more opex.
* PCI requires no consultants, its terms are pretty black and white - you will need an ISA though. HIPAA and can be more of a bear, but your org will need this consultation regardless of whether you own a dc or put it in the cloud. AWS does not give you automatic compliance.
* Yes I can totally believe that working at Google, you'd give TCOs that make Google look good.
Literally none of us except Lyft's operations knows what's good for Lyft. 100 million a year is a ton of cash, but gives them presence around the world. My company has datacenters around the world and it is very operationally complex to maintain them. It's definitely not for everyone, but this guy is making it sound worse than it actually is.