• bahmanm
    link
    fedilink
    English
    arrow-up
    23
    arrow-down
    1
    ·
    1 year ago

    This is quite intriguing. But DHH has left so many details out (at least in that post) as pointed out by @breadsmasher@lemmy.world - it makes it difficult to relate to.

    On the other hand, like DHH said, one’s mileage may vary: it’s, in many ways, a case-by-case analysis that companies should do.

    I know many businesses shrink the OPs team and hire less experienced OPs people to save $$$. But just to forward those saved $$$ to cloud providers. I can only assume DDH’s team is comprised of a bunch of experienced well-payed OPs people who can pull such feats off.

    Nonetheless, looking forward to, hopefully, a follow up post that lays out some more details. Pray share if you come across it 🙏

    • slazer2au@lemmy.world
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      This is part of a series of posts he has done about find out his cloud bill was stupid high because they do computationally heavy software and switching over to collocation. But the whole going from 100% cloud to colo and saving that much money is not to be scoffed at.

      He does say this is an outlier and others won’t get as much roi as they have.

    • palitu@aussie.zone
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      there are a number of blog posts that have different details about the how/why, etc. i just followed the links in the article to other parts of the series.

      I expect that the use case is more prevalent than you think, where you are spending a decent chunk on cloud infra. I have been convinced for some time now that the costs are high compared to our on-prem. I really like the idea of a the “deft” type hardware management service, so that look after the DCs, hardware and connectivity, and we look after the software.