3 ms·
I would think the bulk of it. Given their ride volume, they should be way past the fixed costs for stuff that has to be there before the 1st ride takes place. A
by mv4 8y ago
I would think the bulk of it. Given their ride volume, they should be way past the fixed costs for stuff that has to be there before the 1st ride takes place. API load should be mostly linear as well. Back office, internal reporting, etc anything that deals with data in aggregate can be non-linear, but negligible in the grand scheme of things.
- SilasX 8y agoIn theory, yes, but you might be underestimating how much technical debt can be left behind in a scale-up. For all we know, there's a bunch of stuff that just hasn't been cleaned up. As other comments note, I can totally imagine someone saying "yeah, not worth the risk of breaking something as long as it only comes out to 14 cents a ride". Edit: And, for that matter, they may be using AWS for things other than serving rides, e.g. dev tools and internal service that scale with the number of office employees, not rides.
- mv4 8y agoYeah that $0.14 per ride may sound reasonable, until you realize (as someone pointed out earlier) that it's essentially a EC2 t3.xlarge for one whole hour. Now, imagine that your model requires a 4CPU, 16GB RAM server to handle just one ride per hour - is that really efficient?
- SilasX 8y agoOh, no, I agree it's unreasonable for what they're getting; I'm saying that it might seem small relative to the business priorities.
- solarkraft 8y agoIt didn't sound reasonable to me before, but you really gave me some perspective here. What the the hell are they doing? So much geo processing?