In distributed applications or microservices based on message broker communication, it is difficult to observe the entire lifetime of a…

You know that feeling, right? You’re looking at your Go app’s memory charts, and they’re just… creeping up. Slowly, steadily. Every day, a…

Go 1.27 ships with a new goroutine leak profiler that uses the garbage collector to find goroutines that can never wake up. In this article, we write a leaky program, catch the leak with the new profile, and fix it. - Authored by Cory LaNou

When building a large scale, highly available and distributed system, what
architecture concepts do you need to use, in practice? In this post, I am
summarizing ones I have found essential to learn and apply when building the
payments system that powers Uber.…

Useful resources on distributed system design. Contribute to JohnCrickett/SystemDesign development by creating an account on GitHub.

Just like knowing the basics about how operating system works and/or how memory or CPU work, knowing the basics about database internals will, especially a backend developer, make you a more complete and competent programmer. In the video I'm gonna try to…

Master ClickHouse query optimization through architectural understanding. Learn why ORDER BY design can improve performance 100×, plus proven techniques for trillion-row millisecond queries.

A list of awesome Go tools. Not like awesome-go here only maintains golang awesome tools. - gobuild/awesome-go-tools

Implement transactions using a saga, which is sequence of local transactions

These algorithms aren't magic – but combined they can save over 90% of storage costs and speed up queries. Here’s how 5 common ones work.

Choosing ClickHouse compression algorithms

One photo is a snapshot. A lifetime of photos is an exhibition.

Maybe the same is true of breaking databases? One broken database is a bug. A hundred broken databases…

Kyle Kingsbury, the author of Jepsen, has broken so many databases, he’s turned it…

A framework for distributed systems verification, with fault injection - jepsen-io/jepsen

Chain of thought (CoT) is a prompt engineering technique that enhances the output of large language models (LLMs), particularly for complex tasks involving multistep reasoning.

Learn how to apply the microservices approach to the frontend. A guide to simplifying unwieldy frontends by composing them from small, well-defined units.