3 ms·
This sounds like classic engineer(s) talk; totally ignoring the human cost of setup, maint and ongoing development which is usually handled by an (expensive) op
by ukd1 10y ago
This sounds like classic engineer(s) talk; totally ignoring the human cost of setup, maint and ongoing development which is usually handled by an (expensive) ops team. It's not $5k vs $2k, it's $5k vs $2k + ops time.
- jacques_chester 10y agoIf you run Cloud Foundry (CF), you can get the Heroku experience on your own setup. It works on vSphere, OpenStack, AWS, Azure and GCP is getting there. More platforms are coming. I work at Pivotal, we donate the majority of engineering to CF. We also dogfood it by running Pivotal Web Services (PWS)[0], which is a Heroku competitor. One major difference: PWS (and CF) doesn't have fixed instance sizes. You can specify, to the megabyte, how much RAM you want your app to have. Other resources are dished out proportionally. PWS has thousands of customers, thousands of VMs under management by BOSH, I'm not sure how many apps and services at this point. Last I checked, it's run by about 8-10 people in two shifts (SF and Beijing). [0] http://run.pivotal.io/ http://run.pivotal.io/
- geebee 10y agoI'm not sure what the impact of $5k a month is on a site that needs to scale to 125k requests per minute (I really do mean I'm not sure, I'm not saying this to dismiss the cost). Total costs and revenue might put this in perspective, there are a lot of factors here.
- iLoch 10y agoIt's not $5k vs. $2k + ops time. It's $5k + ops time vs. $2k + ops time. The notion that you don't have to do any maintenance work on a cloud setup is silly, and so too is the notion that a dedicated setup requires full time maintenance.