Lately I have seen developers are nuking the bloat by converting existing applications to hundreds/thousands of ultra slim micro services. I applaud this approach of taking this issue head on at least in server side domains.
Have people taken "Function-as-a-Service" too literally and done the equivalent of moving "is_even" into an AWS Lambda? Or maybe have a dedicated "is_even" nano-service with its own Kubernetes cluster?
They use a Kubernetes “distribution” that adds another layer of automation on top of that!!!
The day is near where “is_even” will be decomposed into multiple containers, with an added caching layer, and extensible authentication layer.
Sounds to me like trading one type of bloat for another.
It's more a way to enforce API boundaries than reducing complexity. I guess when you have some anxiety about your ability to do so otherwise.