|
|
|
|
|
by acdha
1711 days ago
|
|
There's a good post to be written about this but I don't think this is it: it makes a big claim for costs but has almost no technical information and the conclusion is basically treating it as a lead generator for their sales team. The thing which would be more interesting would be talking about the cost savings (~$16/month) relative to things like risks: mostly noisy-neighbor and the administrative concerns of coordinating changes to settings or the security considerations of someone being able to compromise multiple sites rather than just their own. There's no wrong answer there but it's an engineering decision which will lead to different results depending on your environment, budget, and projects. Speaking of engineering, it sounds like they're using some Go code to avoid hitting the limit on certificates and target groups. That's certainly effective but I do wonder how many organizations have enough applications/certificates which are appropriate for shared infrastructure and hit that limit. If your sharing is within that range, the potential cost savings are going to be lower as well. |
|