• 0 Posts
  • 12 Comments
Joined 2 years ago
cake
Cake day: July 6th, 2023

help-circle
  • I can’t argue, but there are benefits.

    If you need something running 24/7 then on-prem may work out cheaper for you. Keep in mind you need a team of server monkeys to keep that running, and your company’s security certifications will come nowhere near that of a major cloud provider.

    Cloud is good for elastic workloads. And you can save money that way if you’re set up for it. A simple lift and shift will always be more expensive. But doing things like moving build tasks to spot instances and auto scaling capacity in peak periods is a huge win. No need to over provision your DC and no need to upgrade your hardware – generally AWS releases new products at roughly the same price as old but with increased performance. You get upgrades “for free”* with no capex.

    Again I’m not saying that your circumstance means that cloud isn’t more expensive. But there are medium term benefits.

    AWS refused to offer hybrid as an option for years. They’ve changed their tune in the past 5 or so. No reason not to take advantage and do what mix makes sense for you.












  • I actually disagree. I only know a little of Crowdstrike internals but they’re a company that is trying to do the whole DevOps/agile bullshit the right way. Unfortunately they’ve undermined the practice for the rest of us working for dinosaurs trying to catch up.

    Crowdstrike’s problem wasn’t a quality escape; that’ll always happen eventually. Their problem was with their rollout processes.

    There shouldn’t have been a circumstance where the same code got delivered worldwide in the course of a day. If you were sane you’d canary it at first and exponentially increase rollout from thereon. Any initial error should have meant a halt in further deployments.

    Canary isn’t the only way to solve it, by the way. Just an easy fix in this case.

    Unfortunately what is likely to happen is that they’ll find the poor engineer that made the commit that led to this and fire them as a scapegoat, instead of inspecting the culture and processes that allowed it to happen and fixing those.

    People fuck up and make mistakes. If you don’t expect that in your business you’re doing it wrong. This is not to say you shouldn’t trust people; if they work at your company you should assume they are competent and have good intent. The guard rails are there to prevent mistakes, not bad/incompetent actors. It just so happens they often catch the latter.