Fan-In: Can we Go faster? | Just a Random Dev Blog
Performance comparison of different fan-in implementations in Golang
languages
golang
Counter Service: How we rewrote it in Rust
The Integrity Data Platform team at Grab rewrote a QPS-heavy Golang microservice in Rust, achieving 70% infrastructure savings while maintaining similar performance. This initiative explored the ROI of adopting Rust for production services, balancing efficiency gains against challenges like Rust’s steep learning curve and the risks of rewriting legacy systems. The blog delves into the selection process, approach, pitfalls, and the ultimate business value of the rewrite.
Go Cheat Sheet & Quick Reference
This cheat sheet provided basic syntax and methods to help you using Go.
How Go’s Error Handling makes you a Better Coder
Write cleaner, stronger code by embracing Go’s error-handling philosophy.
Lets build MapReduce from Scratch - by venkat - Just Build
We will see how to build a MapReduce system from scratch (its workings as well)
Plain Vanilla - Applications
An explainer for developing single-page applications using only vanilla techniques.
javascript
Hunting Zombie Processes in Go and Docker - Stormkit
A technical deep dive into debugging zombie processes in a Go and Docker setup, detailing how I fixed a server crash caused by Node.js process leaks in Stormkit. Learn about process groups, SIGCHLD handling, and using Tini for zombie reaping.
How to run Python in production
The ultimate guide to running Python in Production in 2025
python
Most People Overlook Go’s Concurrency Secrets | by Aryan | Mar, 2025 | Cubed
Concurrency is HARD. Like, really hard. When you need multiple tasks running together, things get messy fast. I’ve spent years fighting with threads and locks in other languages, and man, the race…
The Top 10 Most Common Mistakes I’ve Seen in Go Projects
This post is my top list of the most common mistakes I’ve seen in Go projects. The order does not matter. Now, let’s imagine this Status type is part of a JSON request and will be…
So, I Wrote a Book: The Story Behind 100 Go Mistakes
An brutally honest behind-the-scenes story of writing a technical book from scratch. From burnout to unexpected wins, here's everything I learned while writing 100 Go Mistakes.
Goroutines in Go: A Practical Guide to Concurrency
Let’s face it: modern apps often need to do a million things at once. If your app isn’t set up for that, it can feel clunky and slow. That’s…
Go Optimization Guide
Patterns and Techniques for Writing High-Performance Applications with Go
Timeout Middleware in Go: Simple in Theory, Complex in Practice - Viktor Nikolaiev's blog
What happens when we need different timeout durations for different endpoints? While implementing timeouts might seem straightforward at first glance, the most obvious solution fails silently, frustraiting both users and developers.
Session-Based Authentication in Go
Implementing session-based authentication in Go web applications: a secure and efficient approach.
Go Structs and Interfaces Made Simple
When developers transition to Go from object-oriented languages like Java, C++, or Python, they often struggle with Go’s approach to types a…
Struct Optimizations in Go
In this article we will look into optimizing memory usage and CPU performance by designing our Go structs with the CPU word size and cache line size in mind.
Slice Internals in Go: How the Runtime Expands Slices Efficiently
This article dives into the internals of Go slices, exploring how the runtime efficiently grows the slice’s backing array. It covers the key strategies used, including growth factors, CPU word size alignment, and the size class allocation table, all aimed at optimizing performance while maintaining flexibility.
Bundling Past, Present, and Future
A recent talk I gave about JavaScript bundlers. It’s a bit of a history lesson, and along the way I tried to introduce what bundlers are, why you’d use one, ...
4 Ways of Bumping Major Versions in Your Go Project
I've recently found myself in a rabbit hole of Go major version bumping to v2. What started as a simple task quickly turned into hours of sifting through conflicting information. Should I use a v2 directory? Create a new v2 branch? What about creating a new repository altogether?
The more