Why Operational Costs Start with Infrastructure, Not Code
The real problem about operational costs of (big) projects is usually not the choice of programming language. Talking about some kind of web-based or network service project—which is my main area—, you’ll find JVM or .NET projects as well as Node, Python, Ruby and Go. For sure, Rust found its way to this area, too. And many more are around.
But, when we are talking about operational costs, this written code is mostly only a tiny part. Infrastructure is involved, like Kubernetes. Or at least loadbalancers and so on. Don’t forget your database of choice and more storage you’ll need. The wrong architecture of your project can cost you more money, too.
I’m pretty sure that effective cost reduction starts with infrastructure and architecture, but not with the “right” programming language.