News for hackers. Stuff that matters.
Re:Lyft Files S-1 by halbritt on Friday March 01, 2019 @02:48PM (#19284581)
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.

Network architecture, for example, should suit the needs of the application, but should also be decoupled from the underlying hardware as that hardware is going to evolve.

Compute is fairly straightforward as well. At the data center level, one makes a bunch of 400W holes. What you fill those 400W holes with is relatively irrelevant.

Re:Lyft Files S-1 by eropple on Friday March 01, 2019 @02:54PM (#19284636)
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.

Re:Lyft Files S-1 by halbritt on Friday March 01, 2019 @04:40PM (#19285535)
The thing is, it's not really hard. Quantum computing is hard. Managing IT infrastructure as a value-added component of the business that evolves continuously vs. a cost-center to be bought and forgot is actually not that hard. The only thing hard about that is culture shift.

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.

Re:Lyft Files S-1 by halbritt on Friday March 01, 2019 @04:46PM (#19285602)
As for the OpEx vs. CapEx argument, that's a non-starter.

If you have $100m OpEx per annum, it'll cost you maybe a point or two to convert that to $300m CapEx.

Re:Lyft Files S-1 by peteradio on Friday March 01, 2019 @03:54PM (#19285168)
But what if you had 8m per month?
Re:Lyft Files S-1 by eropple on Friday March 01, 2019 @04:00PM (#19285218)
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."

Re:Lyft Files S-1 by peteradio on Friday March 01, 2019 @04:25PM (#19285402)
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 by spookthesunset on Friday March 01, 2019 @05:45PM (#19286065)
"If the money works in ways a lay man is familiar"

Considering how most layman are completely wrong in their understanding of finance, I'd say that isn't a good endorsement...

Re:Lyft Files S-1 by eropple on Friday March 01, 2019 @04:35PM (#19285494)
I think you're underestimating how much it costs to do what Lyft does. There's a list elsewhere in this thread.