Earlier quoted context omitted.
How would they become a data center company? There are 1000s of huge companies using a mix of colocated DCs, their own DCs, and cloud providers like AWS including the majority of Fortune 500 companies. Most of them are not datacenter companies like QTS.
Most of these companies aren't managing their own data centers at least for areas that use a large amount of compute. Banks and the like that have their own data centers, generally are still using some type of contractor to manage the physical real estate, network connections, ect. even if they are the ones purchasing the servers.
Lyft Files S-1
241–250 of 405 posts
Re: Lyft Files S-1
#242Earlier quoted context omitted.
Uber hosts its own infrastructure, so does Google, so does Facebook. All three of those companies have no problems remaining focused on their business models without turning into a "datacenter company." I strongly dislike the notion that on-prem hosting is somehow a bad thing, or too cumbersome, or otherwise totally solved by cloud providers. AWS specifically is hugely convenient in a number of ways, but it doesn't c…
Google is a bad comparison here IMO because Google IS a datacenter company. No different than Amazon... They run datacenters and offer IaaS to customers, and piggy back off of that. I agree with you on Uber and Facebook though.
Re: Lyft Files S-1
#243Earlier quoted context omitted.
Why not employ an hybrid architecture of bare metal for base load augmented by cloud-based infrastructure for peaks, constructed via a polyglot union of taped-together tools and lubricated by the daily tears of a hundred college hires only to regret it after the engineers who designed it have successfully used it as a springboard for promotion and departed with their accumulated arcane knowledge (and vested shares) f…
Oh come on, you know the performance profile of a streaming service is wildly different from a mobile ridesharing app... Their surges are nothing like yours.
If you have engineers making less than $250k annually, then you have a lot more staff. $8mm monthly is a LOT...
Amazon's clearly making a profit after $8mm monthly.
Re: Lyft Files S-1
#244Earlier quoted context omitted.
Lyft's load varies wildly, with significantly higher traffic on Friday and Saturday nights than e.g. 4 AM on a Tuesday, plus spikes on certain evenings like Halloween and New Year's Eve. Having cloud hosting where we can dynamically grow and shrink based on load saves us a lot compared to having fixed infrastructure that is always provisioned for the NYE peak. Source: I work at Lyft.
Why not employ an hybrid architecture of bare metal for base load augmented by cloud-based infrastructure for peaks, constructed via a polyglot union of taped-together tools and lubricated by the daily tears of a hundred college hires only to regret it after the engineers who designed it have successfully used it as a springboard for promotion and departed with their accumulated arcane knowledge (and vested shares) f…
Re: Lyft Files S-1
#245Earlier quoted context omitted.
At this point isn't it cost-effective for Lyft to just build its own infrastructure?
if I have one job in this life, it's to hang out on hacker news and repeatedly post about how it's not cost effective to run your own infrastructure. 8MM/month doesn't even come CLOSE to needing your own infra. - person who knows how hard it is to run your own infrastructure
> fierro Profile: SWE @ Google Resource & Capacity Planning
I think you mean "Person who's job it is to convince others it's really hard and they should just buy your product"...?
Re: Lyft Files S-1
#246Earlier quoted context omitted.
2017 Compared to 2018 * As a percentage of revenue, cost of revenue decreased from 62% to 58%. * As a percentage of revenue, sales and marketing expenses decreased from 54% to 37%. These seem to be positive signs.
This also implies that the vast majority (if not all of their) loss is sales and marketing.
Re: Lyft Files S-1
#247Earlier quoted context omitted.
Respectfully, having read your other comments: I'll answer that question if you demonstrate to me an understanding of the difference between $300M/3 years capex and $8M/month/3 years opex. If you do that, though, my answer will be "right, so we're done here."
I'm mostly just having a laugh so I won't be able to explain the difference. If the money works in ways a lay man is familiar I'd expect I would be able to afford the necessary man power and equipment so far under 8m per month after equipment purchase that I don't really need to know the details of the finance opex/Capex difference. I really appreciate you taking the time to bring up your good points.
Re: Lyft Files S-1
#248Earlier quoted context omitted.
100M/year is ~8M/month. Some perspective on that, it could by you one of: ~400PB of data in S3. ~2600 bare metal "x1 type" ec2 instances running 24/7, 3 year upfront reservation. ~60M Write IOPS in dynamodb ~300M Read IOPS in dynamodb ~3500 16xl RDS aurora instances Again, each of those is spending the entire budget on a single service, but that seems like a nonsense level of spending. Maybe they really have that muc…
At this point isn't it cost-effective for Lyft to just build its own infrastructure?
Re: Lyft Files S-1
#249Earlier quoted context omitted.
Google wasn't really a cloud provider for like 15 years and hosted their own infrastructure that entire time.
That's not exactly fair, the first decade+ of that pre-dates the public cloud.
Re: Lyft Files S-1
#250Earlier quoted context omitted.
If you've built a heterogenous environment at the end of three years, then you've failed. The reason that AWS, Google, Azure, et.al do so well is that they don't just buy some servers. They do actual capacity maangement, and not a very good job of it I might add. They also manage the lifecycle of every component in the infrastructure such that the next iteration of that component is understood and interchangeable. Ne…
Fully agreed on all points. But it remains a really hard problem. And when you start to do it out at the scale of something like Lyft, you're gonna blow through your available parts of that $300m (because you can't spend it all up front, obviously) pretty quick. The care and feeding of fleets of (physical) machines is really, really hard and not to be underestimated.
It's all about leadership. The dearth of skilled leadership is the issue. I'd wager this is how some FAANG companies are managing this. They're hiring people that know what they're doing. One doesn't need to design and build their own servers and network hardware to do well at the scale of folks like Dropbox or Lyft.
Cloud adoption is all about making the issue someone else's problem, which is only kicking the can down the road. Eventually, every company that does a thing will realize that their survival is contingent upon becoming a software company that does that thing.