3 ms·

> opinions like this is why I end up having to deal with 800k/month aws bills and 3 hour deploys.. How exactly would a "private" cloud save you from these clea

• cyberpunk 10y ago
  It's pretty easy for a team to go rogue and if they have their own AWS account end up in a total mess and solving their problems with hardware. I've been at places where the exact same problem is being solved by several different teams and I think a lot of that was down to that the availability of AWS for instance allowed them to go total silo and act almost like a vendor to the other teams which consumed their apis. Going back on prem really helped, even if maybe it was just the "group project" to do it. Afterwards though I think there's a bit more buy in simply because the company has total ownership of the stack. Some team starts thrashing resources there's a bit more knowledge sharing and the stakes are higher (at least, the resources aren't limitless). You're running your service in AWS and another team consumes it, then RDS starts getting slower what can you do? Blame AWS when you get a nasty call from a PM and go to lunch... On prem? You're probably not far from the DBA who can explain what's happening and you can grab the consumer of your service to help too. It seems to just open thing up a lot.. YMMV. I've seen a definite improvement culturally though.