https://ecostack.dev/categories/go/ Recent content in Go on Ecostack Hugo -- gohugo.io en © 2026 Sebastian Scheibe Fri, 02 May 2025 16:05:19 +0800 https://ecostack.dev/posts/fixed-window-rate-limit-golang-redis/ Fri, 02 May 2025 16:05:19 +0800 https://ecostack.dev/posts/fixed-window-rate-limit-golang-redis/ Introduction # Imagine you have a resource that can only handle a limited number of requests per second. How do you ensure it doesn’t get overwhelmed? One solution is rate-limiting — controlling how many requests are allowed in a given time frame. In this article, I’ll show how to implement a simple rate limiter using Redis and Golang. Rate-Limiting Algorithms # There are several types of rate-limiting algorithms — two common ones are fixed-window and token bucket. https://ecostack.dev/posts/golang-error-missing-location-in-call-to-time-in/ Mon, 04 Mar 2024 08:24:25 +0800 https://ecostack.dev/posts/golang-error-missing-location-in-call-to-time-in/ The Problem # Did you ever have any of these errors? missing Location in call to Time.In missing Location in call to Date panic: time: missing Location in call to Time.In goroutine 1 [running]: time.Time.In(...) /usr/local/go/src/time/time.go:1146 main.main() /app/main.go:16 +0x1c5 Does your code look somewhat like this? location, _ := time.LoadLocation("Europe/Amsterdam") name, offset := time.Now().In(location).Zone() log.Println("name: "+name, "offset: "+strconv.Itoa(offset)) Are you using Alpine or a similar distribution in your Docker container? https://ecostack.dev/posts/golang-int-to-string/ Tue, 08 Aug 2023 23:11:10 +0800 https://ecostack.dev/posts/golang-int-to-string/ The Go standard library offers the strconv package which has two functions to convert an integer to a string. In the following, let’s go into detail on how and where to use which one. strconv.Itoa(i int) string strconv.FormatInt(i int64, base int) string For converting an integer to a string, the strconv.Atoi(s string) is the best method. strconv.Atoi(s string) string Integer to String # strconv. https://ecostack.dev/posts/go-and-cgo-cross-compilation/ Wed, 16 Nov 2022 23:51:02 +0800 https://ecostack.dev/posts/go-and-cgo-cross-compilation/ Updated on 2023-05-24: Added information on cross-compiling using the MUSL and GNU toolchain on macOS for static linking. Updated on 2025-01-08: Updating the parameters for static linking. Introduction # With the release of Go v1.5, it became possible to cross-compile applications for various targets such as Windows, macOS, Linux, Solaris, and Android. Cross-compilation allows you to build binaries for different operating systems from a single development machine. This article explains how to cross-compile Go applications, including those that use Cgo for C dependencies. https://ecostack.dev/posts/go-errors-with-stacktrace/ Sat, 04 Jun 2022 00:09:16 +0800 https://ecostack.dev/posts/go-errors-with-stacktrace/ Problem # The error handling of Go is not up to snuff compared to other languages like Java for example. Errors are treated equally to other values, meaning, they have no special type. This means, they do not carry information of origin in them. Which makes tracking down the error origin more difficult. Let me show that to you. package main import ( "errors" "fmt" ) func main() { err := NewErrorWithStackTrace() if err ! https://ecostack.dev/posts/go-generic-option-type/ Fri, 03 Jun 2022 22:53:54 +0800 https://ecostack.dev/posts/go-generic-option-type/ Introduction # You might have heard of the Option type, if not, let me introduce that concept shortly. An Option type is data structure which either has a value or no value contained in itself, it kind of acts as a box (Schrödinger’s cat 😉). Usually, the Option type is created with a constructor such as Some(value) or None(). From there, the type usually offers methods which can act in case a value exists. https://ecostack.dev/posts/goroutine-variable-scope/ Sun, 29 May 2022 00:01:06 +0000 https://ecostack.dev/posts/goroutine-variable-scope/ A goroutine can capture a variable from the surrounding function. Whether a loop gives each goroutine a separate variable depends on how that variable is declared and which Go language version the package uses. For modules declaring go 1.22 or later, variables declared by a loop have a new instance on each iteration. The common loop-capture bug shown in older Go tutorials therefore no longer applies to those declarations. Variables declared outside the loop can still be shared.