@laurel

> Why are microservices still pushed so hard?

It appeals to engineers because they can, in theory, make small tools that do one thing (although too few of them think about fitting it together and they end up with a rats' nest). It appeals to managers because of provisioning: GCE, AWS Lambda, etc., fine-grained access control of repositories, the promise of automatic compliance with various absurd regulatory boundaries (the same ones that made everyone start requiring 2FA for everything).

> 2. I've noticed the same people pushing for microservices, push for "immutable" OS type standarization.

Yeah, you know, all of the commercially available bananas are clones, they're all genetically identical. We get an aggressive enough fungus, that's it for bananas for a few decades.

And, you know, ASLR and stack canaries and whatnot, but I think it's better to locally source your binaries rather than having purely identical ones. It is way easier to write an exploit for a process that is executing a binary that you have, you know where everything's gonna be, you know how paranoid the compiler settings were.

> gRPC

It's like job queues and graph databases were, it's a buzzword for something almost no one needs but GOOGLE SCALE. See the following old-ass article about exactly the same thing: http://widgetsandshit.com/teddziuba/2009/06/startups-keep-it-in-your-pants.html .