Observability in Go, from signals to alerting

Concurrency is less about “starting async work” and more about owning its lifecycle. In .NET, I’m used to thinking in terms of Task, async/await, and CancellationToken. With Go, simply writing:

Hello developers, I would like to share all code I developed in the last 4 years. It is a trading platform made in Go and split into several microservices. What you can find here: A (small) gateway in

https://codeberg.org/tslocum/list2regexp Here is an example. Given the following list of strings: 1.2.3.4 127.0.0.1 127.0.0.2 127.0.0.11 128.0.0.1 125.0.0. 200.0.0.1 2001:0db8:85a3:0000:0000:8a2e:0370

Hello. I'm seeing a goroutine scheduling oddity that I don't understand. Can anyone explain why this is? I have a function which occasionally writes to a file. I noticed that this was taking longer th

What actually holds up when you build observability into a Go service, backed by a real measurement instead of a rule of thumb - signal placement, cardinality, dashboards, alerting, and PII, not anoth

I'm running into what I suspect is a goroutine leak in a CLI tool I'm building. Long-running commands seem to leave goroutines hanging around after the operation should be done, and memory creeps up o

It took a while to marry together an architecture that supported server-side events while making sure the rest of the application was decoupled from them. I found that a lot of posts were myopic and s

First thing first, shout-out to the engineer who created wails. For learning purposes, I went into the rabbit hole of trying to convert go binary to desktop app and now android mobile app. The wails3