4 ms·

> One could easily imagine that the performance and stability should be a lot higher than with Heroku. No, I can’t imagine that. Why would performance be any d

> One could easily imagine that the performance and stability should be a lot higher than with Heroku. No, I can’t imagine that. Why would performance be any different? I imagine most of these kinds of solutions use Docker behind the hood anyway, so they’re likely to be identical.

danielheath 5y ago
Because Heroku is phenomenally expensive.
- appliku 5y ago
  As i said in another comment Heroku is unbelievably expensive. What they offer for $250 per process can be done at $60/mo per whole app. When I helped them move all background workers and all non-production apps to Digital Ocean they ended up saving $7k/mo which blew my mind. It is easy to start on Heroku, but staying there is a black hole in any budget. Thankfully we've built Heroku Config Vars sync so one can move off of Heroku gradually.
  - fnomnom 5y ago
    >Heroku is unbelievably expensive. only if developer/devops/admin time is free and for most it isnt. if 60 vs 250 /month is a breaking factor for you and your use case: go for it. if you need the software deployed to make real business it just doesnt matter.
    - appliku 5y ago
      $250/mo per process. And with appliku it is done automatically so there is no need for admin/devops time.
    - capableweb 5y ago
      > if you need the software deployed to make real business it just doesnt matter No wonder AWS can get away with the prices they have since people like you (and many more VC funded startups) simply have zero care about the price. For people who run "real" businesses (meaning you need to have a larger income than expense [meaning, everything not VC-funded]), price is always a part of the calculations, even when it comes to hosting.
capableweb 5y ago
See https://news.ycombinator.com/item?id=28468943 https://news.ycombinator.com/item?id=28468943 To clarify, I mention "performance" in terms of the speed of "from commit to deploy", not the CPU/IO performance of an already deployed application.
- RussianCow 5y ago
  That makes more sense, but the deploy cycle is already really fast with Heroku. I'm not sure if there is very much value in trying to shave off a few more seconds.
  - appliku 5y ago
    Depending on your requirements build ties in Heroku can be quite long. One app i’ve recently observed take 7 minutes to build because it always had to build both JS and Django parts(buildpacks for both were executed every time). We made it way faster with custom docker file that used caches and often built under 40 seconds. i am not saying that is not doable in Heroku, but would take more effort.

danielheath 5y ago

Because Heroku is phenomenally expensive.

appliku 5y ago
As i said in another comment Heroku is unbelievably expensive. What they offer for $250 per process can be done at $60/mo per whole app. When I helped them move all background workers and all non-production apps to Digital Ocean they ended up saving $7k/mo which blew my mind. It is easy to start on Heroku, but staying there is a black hole in any budget. Thankfully we've built Heroku Config Vars sync so one can move off of Heroku gradually.
- fnomnom 5y ago
  >Heroku is unbelievably expensive. only if developer/devops/admin time is free and for most it isnt. if 60 vs 250 /month is a breaking factor for you and your use case: go for it. if you need the software deployed to make real business it just doesnt matter.
  - appliku 5y ago
    $250/mo per process. And with appliku it is done automatically so there is no need for admin/devops time.
  - capableweb 5y ago
    > if you need the software deployed to make real business it just doesnt matter No wonder AWS can get away with the prices they have since people like you (and many more VC funded startups) simply have zero care about the price. For people who run "real" businesses (meaning you need to have a larger income than expense [meaning, everything not VC-funded]), price is always a part of the calculations, even when it comes to hosting.

capableweb 5y ago

See https://news.ycombinator.com/item?id=28468943 https://news.ycombinator.com/item?id=28468943 To clarify, I mention "performance" in terms of the speed of "from commit to deploy", not the CPU/IO performance of an already deployed application.

RussianCow 5y ago
That makes more sense, but the deploy cycle is already really fast with Heroku. I'm not sure if there is very much value in trying to shave off a few more seconds.
- appliku 5y ago
  Depending on your requirements build ties in Heroku can be quite long. One app i’ve recently observed take 7 minutes to build because it always had to build both JS and Django parts(buildpacks for both were executed every time). We made it way faster with custom docker file that used caches and often built under 40 seconds. i am not saying that is not doable in Heroku, but would take more effort.