[HN Gopher] Heroku 22 Stack
___________________________________________________________________
Heroku 22 Stack
Author : nikodunk
Score : 96 points
Date : 2022-06-15 16:17 UTC (6 hours ago)
(HTM) web link (devcenter.heroku.com)
(TXT) w3m dump (devcenter.heroku.com)
| veesahni wrote:
| We use it for mini supportive apps, but have the core of our
| product on AWS directly.
| superb-owl wrote:
| Are folks still using Heroku in prod? Curious what the experience
| is like these days, and if it's as limiting as it used to be.
| the__alchemist wrote:
| Yep! Using it to run a scheduling webapp for a number of
| fighter squadrons.
| EToS wrote:
| Switched to GCP Cloud Run.. but do miss the Heroku CLI
| sometimes
| vdfs wrote:
| The fact that minor change like this made it to front page mean
| it's still used, there no better altrenative. From a happy ~7
| years customer
| bkovacev wrote:
| We do - the monthly bill was about 30k when I joined and I was
| able to drop it down to 15k in a month by refactoring the
| majority of the infra (mainly backend workers). DB is the
| biggest limiting factor - pricing is absolute rubbish. You
| can't have backups after your data size goes above 20gb.
| Replicas have to be on the same tier, as otherwise lag occurs
| daily. Connection limits are awful, but luckily you can setup a
| pooler in front of the DB. Also, we had workers being stuck in
| a limbo state, where they aren't crashed, but they aren't
| working either - but this mainly happens with Celery workers,
| to be fair. Some add-ons are also cheaper directly on their
| respective website, rather than through heroku.
|
| If someone was to use heroku I'd advise to at minimum:
|
| - move the DB elsewhere.
|
| - not setup external services through heroku auth (sentry,
| logtail, newrelic etc)
|
| With all of that said - I do have my startup and some pet
| projects there as it does in fact abstract the devops aspect
| away.
| scraplab wrote:
| Our database is north of 20GB and backups work fine. They
| made improvements to this in Jan 21, which might have
| improved this? https://blog.heroku.com/faster-postgres-
| backups
| vdfs wrote:
| Ours is 170Gb and backups work, but it have continues
| protection which is always available no matter the size of
| the DB, but i think OP mean dumps that he can download and
| store offsite
| bkovacev wrote:
| You're right, my bad! Regarding continuous protection
| that works flawlessly as it has saved us 2-3 times
| already!
| bkovacev wrote:
| We have a:
|
| - ~500gb one fails to backup
|
| - ~1tb one fails to backup
|
| - ~100gb one succesfuly backups
|
| The link where I got that number is here -
| https://devcenter.heroku.com/articles/heroku-postgres-
| backup...
| cpursley wrote:
| Why haven't y'all moved to Render.com already? It's awesome;
| It's like as if Heroku never stopped innovating and much
| cheaper.
| yoran wrote:
| What does Render.com do that Heroku doesn't? (seriously
| asking)
| cpursley wrote:
| Free static sites, no daily restarts, easy docker and
| handles distributed Elixir which is huge for us. I
| haven't had to touch our infrastructure for a year.
| your_username wrote:
| I'm actually in the process of moving a large monolith from
| EC2 to Heroku and this is exactly what the plan is: our DB (>
| 10TB) is on RDS; ES, Redis also are from AWS. Third-party
| services aren't provisioned through the marketplace, instead
| straight through the vendor. Right now this is Datadog and a
| bug reporter.
|
| We're extremely overprovisioned on EC2 as it is (peaking at
| 54GB consumed RAM over the last 12 months, and we have 386GB
| available) so management is welcoming the change to a bunch
| of Performance L dynos!
|
| We're moving to Heroku for a variety of reasons -- least of
| which is their recent fiasco -- primarily dev exp and
| Pipelines/review apps (still supported!). Both will give our
| developers a vastly superior experience to what they had:
| nothing (we desperately need it).
| flatiron wrote:
| Nobody ever got fired for hiring IBM but I think people may
| get fired now a days for moving to heroku! Good luck! I
| would love to hear an update in 12 months if you are still
| there / heroku is still running.
| aabhay wrote:
| We had ~10 apps on heroku until last month. We have been
| migrating to Cloud Run and Cloudflare Pages recently and love
| it.
| yoran wrote:
| For sure. As the only developer in the team, it saves me a
| bunch of devops time that I can instead dedicate on the
| business, while we're trying to get product-market fit.
|
| I'm sure that there are limitations for larger teams or if you
| have specific requirements. But I think it's a great choice if
| you're a small team and/or your application is more or less
| run-of-the-mill from a technical point of view.
| wbobeirne wrote:
| Was on it until late last year, switched off recently. The cost
| for the performance and reliability of their Redis and Postgres
| instances was pretty bad, and it didn't seem like the dynos
| were well co-located with the db. A few of the issues we had:
| 1. Redis was wildly unreliable, would go down for 2-5 minutes
| every few days with no explanation from support 2. We had
| to pay for a much beefier instance of Redis just to increase
| our connection count. We weren't using more than 2-3% of the
| available memory, we just needed the connections, but you can't
| pick and choose. 3. Their limits on websocket connections
| were also a killer, I think each dyno could have a max of like
| 1,000 sockets so we had to add more dynos just for more
| sockets. 4. Switching over to AWS reduced the RTT (just
| networking, not actual query runnig time) on Postgres queries
| from ~8ms to ~1ms. Seems like the dynos and db weren't closely
| co-located.
|
| However, the amount of time spent and code we have to maintain
| our infrastructure is waaay more than it used to be on Heroku.
| No free lunch for sure.
| bvirb wrote:
| We're happily using Heroku in prod.
|
| One nice thing for us is that we also use Heroku CI so our
| tests run on the same infrastructure as prod, and the pricing
| for Heroku CI is just based on usage with no concurrency limits
| so everyone can have their CI runs across all their branches
| happening at the same time. We tried Github Actions when Heroku
| CI was _ahem_ "down" and it was slower & more expensive + the
| concurrency limits meant we had to wait in line to get a CI run
| though. Nobody else seems to use or even talk about it though,
| so either we have a crazy CI setup or Heroku just never
| marketed it.
|
| We occasionally do the math to see if Heroku is still a good
| deal and the answer is always that the amount of time we
| estimate we're saving on devops more than pays for itself in
| extra time spent on app development. There's a break-even where
| that will no longer be the case, but as engineering & devops
| get more and more expensive Heroku seems like a better and
| better deal.
|
| The scariest part isn't really the product itself but all the
| recent talk about how it's a ghost town and nobody works there
| anymore. It's a great product but I do hope they start
| innovating again.
| elsurudo wrote:
| I've been using it in prod for almost 10 years now, almost
| without issues. Personally I'm still a very happy customer.
| FWIW, it's a low-traffic app, so cost isn't an issue. I'm happy
| to pay Heroku a bit more for the developer ergonomics over
| running my own server - it has saved me a ton of time.
|
| Luckily I was not affected by the recent "issues", since I'm
| not using the Github integration.
| johnbellone wrote:
| I've had to recently approve a surprisingly large bill for
| Heroku.
|
| For small teams/products/services it totally makes sense. After
| a certain point, especially in a large organization that
| understands the value in infrastructure/operations investment,
| most applications/services can be streamlined and deployed. At
| that point, no, it is much much cheaper to go elsewhere.
| arnley wrote:
| it's alive!
| [deleted]
| [deleted]
___________________________________________________________________
(page generated 2022-06-15 23:01 UTC)