Kevin Tung·2d agoGOGC Alone Peaked Past 600 MiB. Our 512 MiB Container Got OOM-Killed 3 Times Out of 3.GOGC=100 alone peaked past 600 MiB and died 3/3 under 512 MiB. GOMEMLIMIT=460MiB held ~448–450 MiB with 0/3 OOM.A response icon1A response icon1
Mojtaba (MJ) Michael·Feb 27Golang Reflection: The Guide to Runtime Type Inspection, Manipulation, and Best PracticesWritten By: MJ Michael (Mojtaba Michael)
Miah Md Shahjahan·Oct 12, 2025Why Python Threads Wait & Go’s Don’tIn Python, only one thread runs Python code at a time. The Global Interpreter Lock (GIL) ensures this, while the operating system (OS)…
Asaduzzaman Sohel·Oct 5, 2025The Journey of a Request in a Go Web AppToday I’ll walk you through the full cycle of how a request comes into a Go web app and how the response goes back to the client.
Alexander Obregon·Sep 16, 2025Escape Paths in Go ClosuresClosures in Go capture variables from their surrounding scope, but the way those captured values are stored and tracked involves some…
Alexander Obregon·Sep 16, 2025Memory Scavenger in Go RuntimeEfficient memory management is one of the most important parts of the Go runtime. Applications allocate space on the heap for objects, and…
Alexander Obregon·Sep 13, 2025Package Initialization Order in Go ModulesPackage initialization in Go follows a fixed sequence that the compiler and runtime control. The order is never random and never left to…
Furkan·Sep 11, 2025Inside Go — How It Really Works: Series KickoffToday I’m kicking off a new series: Inside Go — How It Really Works. The goal is simple — to explore Go from its core internals to the code
Alexander Obregon·Sep 2, 2025Defer with Function Arguments and Timing in GoGo’s defer statement is one of the language’s most recognizable features. It lets developers line up function calls to run after the…
Sifat99·Aug 30, 2025Client-Server Request-Response Handling with Go and Unix-based Systems at the OS LevelHow Client–Server Communication Really Works (Through the Lens of Go and Unix Systems)A response icon1A response icon1
