Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There's an entire part of all the build tools that handles configuration and secret management. Here's an example:

https://learn.microsoft.com/en-us/azure/devops/pipelines/pro...

They've always had this stuff. Back in the day it used to be XML transforms. I know azure have added key vault in recent years as well so you can get the values from the key vault instead, but it seems a cynical cash grab to me.

For loading balancing, there's a reason the load balancing servers all have APIs.

Almost no business will save money scaling. Think about it. Most businesses are small and medium business that just don't have the volume of traffic to justify anything more than buying or renting a single/two servers vs the cost of having a scaling solution in place. There are only a small number of businesses (in the scheme of things) that benefit from scaling as you have to pay to do it. And even then the saving is often so miniscule compared to a dev salary you lose money paying people to even set it up and will NEVER recoup that cost.

The cost of even having a single meeting with 4 people about it is more than the saving over a year.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: