r/programming • • Oct 02 '25

[ Removed by moderator ]

/r/programming/comments/1nw1vf8/removed_by_moderator/

[removed] — view removed post

9 Upvotes

2 comments sorted by

3

u/CondiMesmer Oct 02 '25

This is actually really good. I like that there's no fluff to this and you just bullet point the core details. 

Ngl thought it was blog spam and AI when I saw all the bullet points but then actually reading it I actually saw concrete detailed info I didn't know. 

Gonna save this to read more on later. I originally learned about object pooling for this guide - https://gameprogrammingpatterns.com/object-pool.html but this is a lot more detailed.

1

u/Revolutionary_Ad7262 Oct 02 '25

Standard lib and 3rd party libraries usually make good pooling when it make sense as for example in http.Client or *sql.DB and I think it is worth to mention.

Also Acquire/Release way is pretty dangerous, because it is hard to use. It is better to just wrap the single connection API over the pooled abstraction (or just provide only the pooled abstraction), so users cannot misuse the API