Let's dive into the world of graceful shutdowns, specifically for Go applications running on Kubernetes.
Go 1.26's new garbage collector: measure before you upgrade
The piece to sit with covers Go 1.26's new garbage collector, now on by default, and argues the gains are real but unevenly distributed, so it walks through what to measure on your own workload before flipping the switch. It pairs nicely with a separate write-up on real-world Go versus benchmark obsession, which makes much the same point from the other direction. Elsewhere there is a practical guide to graceful shutdowns for Go services on Kubernetes, and a nicely odd project building an append-only log directly on object storage, no broker in sight.

The piece to sit with covers Go 1.26's new garbage collector, now on by default, and argues the gains are real but unevenly distributed, so it walks through what to measure on your own workload before flipping the switch. It pairs nicely with a separate write-up on real-world Go versus benchmark obsession, which makes much the same point from the other direction. Elsewhere there is a practical guide to graceful shutdowns for Go services on Kubernetes, and a nicely odd project building an append-only log directly on object storage, no broker in sight.
This is the weekly thread for Small Projects. The point of this thread is to have looser posting standards than the main board. As such, projects are pretty much only removed from here by the mods for
Build an append-only log on object storage in Go using immutable segments, a bounded catalog, writer fencing, and replay by LSN or timestamp—without a broker.
The new collector is on by default. The gains are real, and they are not evenly distributed. Continue reading on Medium »
Hello everyone, let me introduce myself — I’m Ahmad Yusup. Lately, I’ve been learning the Go programming language, and I’d like to share a… Continue reading on Medium »
Imagine dropping a Formula 1 car onto a super muddy, pothole-filled country road. Or actually, let’s say you release a really sleek… Continue reading on Medium »
Deadlocks, goroutines, WaitGroups, and buffered vs unbuffered channels — explained by someone who just figured it out Continue reading on Level Up Coding »
Stop guessing and start using pprof and trace to find real bottlenecks. Continue reading on Level Up Coding »
Golang Monolith Mastery Course: ...
Golang mutex vs channel is the concurrency question interviews actually ask, and one rule decides it: share memory, use a mutex ...
Golang Monolith Mastery Course: ...
Learn Golang in 6 minutes: the six ideas that actually are Go, for developers who already write JavaScript or Python and keep ...
Golang GoProgramming GoLang GolangCheatSheet Programming Coding Developer SoftwareDeveloper ภาษาGo ...


Co-authored-by: xinghewumeng


Co-authored-by: xinghewumeng

Co-authored-by: xinghewumeng

