• 0 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: July 9th, 2023

help-circle


  • A properly architected and implemented microservice architecture optimizes work throughput while minimizing risk. In practice its architecting in such a way that no part can take down the whole individually - the very opposite of a monolith where everything is inseparably interdependent at some level.

    Problem is, most organizations don’t know how to properly architect for and integrate microservice architectures into their environments and work process. Most think that a crew of former sysadmins can just spin up a few saas services, slap some autoscaling on it if they’re feeling spicy, segment along traditional monolith “frontend/backend” lines for “security,” and call it a day. They then spend time and money learning and/or fighting this system, only to see minimal (if any) improvement in work capacity/quality and instead end up with an outsized cloud bill.




  • You know that “anti commercial AI license” shit does nothing, right? It’s the equivalent of idiots posting that wall of text on Facebook a decade or so ago saying they don’t give Facebook permission to use their pictures, posts…etc.

    I mean if it makes you feel better and gives you a sense of control in an otherwise out-of-your-control environment then I suppose go for it, but you’re not actually accomplishing anything other than making yourself feel slightly better and more deluded.














  • Not my personal setup, but I’ve worked at orgs in the past where the tier0 infra was set up using terraform and all funneled through github PRs. To add users/gain access to resources…etc, users would submit a PR and someone on the IT team would review/reject accordingly. It allowed for scalability and version/config control, but still required human input for the actual security question decision making.