@glyph @collinsworth @danilo > “why call a function in a library when instead you could spin up a kubernetes pod that consumes $1500/mo of AWS spend”

This is a question I've asked so many times at so many companies, though phrased slightly differently (why does this have to be a micro service partitioned by the network and living in a separate repo, instead of a simple function in a module) and hardly ever gotten an intelligent answer to. It generally boils down to perceived needs that never materialize. Or because they think they're following best practices.

All they are doing is increasing accidental complexity. Exactly the thing they should be minimizing. It's frustrating.