Hey everyone! Go 1.26 arrived in February 2026, six months after Go 1.25. And it came with changes that will directly impact performance and the way you write Go code. The main highlight is the n...

Hey everyone! In Go, errors are values. There are no exceptions: you return error and the caller decides what to do. This model is simple, but it requires knowing how to create, propagate, and che...

Hey everyone! Most Go services don’t need to be concurrent. I’m not saying Go shouldn’t use goroutines or channels. I’m saying that premature concurrency - adding goroutines, mutexes, and channel...

Hey everyone! gRPC is one of the most powerful technologies for building modern APIs. Excellent performance. Strong typing. Native streaming. Used by Google, Netflix, Uber, and other giants. But ...

Hey everyone! Migrating a Go application to Kubernetes seems simple on paper. You create a Dockerfile, deploy it, and you’re done, right? Wrong. In practice, you encounter problems that don’t ap...

Hey everyone! Writing Go code that works is one thing. Writing idiomatic Go code, that follows the language’s principles and conventions, is completely different. Idiomatic code is more readable,...

Hey everyone! When it comes to data serialization in Go, JSON is almost always the default choice. But what’s the real cost of that decision? How much CPU, memory, and latency are you wasting with...

Hey everyone! Today we’re diving into rate limiters, one of the most critical topics for high-performance APIs, public services, distributed systems, and platforms that must limit abuse. Why ra...

Hey everyone! Today I want to walk you through something that almost nobody explains clearly: what Terraform actually executes when you run a provider written in Go. We often assume Terraform “c...

Hey there! Implementing systems from scratch is one of the best ways to deeply understand how they work. In this article, I present an educational project: a Redis-like Key-Value Store fully imple...

Hey everyone! Today I want to talk about one of the most elegant and misunderstood ideas in Go: context.Context. Many people use it without much thought — “because the framework requires it” — but...

Hey everyone! In recent years, we’ve seen Rust, Python, Java, Kotlin, and even Zig trying to invade Go’s space in the Platform Engineering world — but the fact is: in 2025, Go continues to be t...

Hey everyone! This post is a deep dive into a very common myth in the Go ecosystem: “Go doesn’t have cold start”. Spoiler: Go tends to be faster than Node/Python in many scenarios, but Go’s cold ...

A misconception among many developers is believing that a concurrent solution is always faster than a sequential one. This couldn’t be more wrong. The overall performance of a solution depends on m...

Hey everyone! Today I’m going to do a complete performance analysis of the main HTTP routers in Go. Let’s see who’s really the fastest, who consumes less memory, and which is the best for each sce...

Hey everyone! You have a project ready, but now comes the question every developer faces: where to deploy? Vercel, Netlify, or Railway? The choice isn’t obvious and can directly impact your projec...

Hey everyone! Today I’ll show you how to create a resilient distributed tracing system using Apache Kafka and Jaeger. The idea is simple: what if Jaeger goes down? Do you lose all traces? No! We’l...

Hey everyone! Today I’ll show you how to create a custom Terraform provider from scratch using Go. It’s a topic that many developers are afraid to tackle, but it’s actually not the seven-headed bea...

Hey everyone! Today I’m going to show you how to create a Kubernetes Operator from scratch that monitors ConfigMap changes and sends events to a webhook. It’s a super useful feature for hot reload...

Hey everyone! Today I’m going to show you why senior engineers are abandoning the MVC pattern in Go and migrating to more modern architectures. If you’re still forcing Go into a pattern that doesn...