tookledoodle

No, it objectively remains an edge case, no matter whether it is for me or you or the person you’re replying to or whatever. Your customers doing inefficient things does not change the fundamentals of the situation. And the other testing that didn’t focus on cold starts looked like basically a non-result looking at the graphs, so I didn’t bother talking about it. I can, though, with the understanding that it will strengthen my point.

You call out PHP in both the blog post and this comment, which is interesting, because persistent pooling has been a part of PHP (and advised) for years.

Which leaves serverless and scripts (your other example from the blog post). Which, let’s be honest, are both edge cases at this point in time. Maybe that’ll change, but today it’s true.

Twenty year SRE here backing up the person you’re dismissing: you’re optimizing an edge case. Literally step one of operationalizing every system in existence is burying your DB behind a pooler. 100ms off a connect call in a script is not useful. The serverless improvement has some potential, but one would be forgiven for asking why you’d use an environment which doesn’t let you speak network protocols you’d like to speak.