For engineers in charge of supporting Go applications, diagnosing and resolving memory issues such as OOM kills or memory leaks can be a daunting task. Practical and easy-to-understand information about Go memory metrics is hard to come by, so it’s often challenging to reconcile your system metrics—such as process resident set size (RSS)—with the metrics provided by the old runtime.MemStats, with the newer runtime/metrics, or with profiling data.

Goja is an implementation of ECMAScript 5.1 in pure Go with emphasis on standard compliance and performance.

Golang library for end-to-end Go-Typescript type safety.

otelsql is an instrumentation library for the database/sql library of the Go programming language. It generates traces and metrics from the application when interacting with databases. By doing that, the library allows you to identify errors or slowdowns in your SQL queries that potentially impact the performance of your application.

Learn how PGO improves use of inlining and CPU instruction caches. I show how to get biggest boost for your projects by using the right CPU profile

Best practices for handling context plumbing.

IntegreSQL manages isolated PostgreSQL databases for your integration tests.

This post covers a range of topics related to building services in Go, including:

- Structuring servers and handlers for maximum maintainability
- Tips and tricks for optimizing for a quick startup and graceful shutdown
- How to handle common work that applies to many types of requests
- Going deep on properly testing your services
- From small projects to large, these practices have stood the test of time for me, and I hope they will for you too.

This article is a practical look at reducing dependencies in Go libraries. We'll start by looking at how Go dependencies work, then go into a few ideas around reducing dependencies. Finally, we'll go into a few ways I've implemented these ideas in Huma and the results. Hopefully you can use some of the same techniques in your own projects.

The backend engineering team at Nurdsoft is a fan of Go, we use it for almost all of our backend services, its easier to get started even our Frontend engineering team can write Go!. This article is about how we can use Go to automate a browser virtually acting like a real user.

When starting a project, new Gophers often ask the following questions.

- What logger should I use?
- What web framework should I use?
- What object–relational mapping (ORM) should I use?

These questions are well-intentioned but they all miss a key aspect about Go.

As someone who works a lot with operating systems, there are many scenarios that require loading C libraries. Plugins that use shared libraries, low-level device APIs, random Linux utilities. Despite modern options for interprocess communication, sometimes you get a header file and a shared object and have to run with it.

This post covers cgo, Go’s C interoperability layer.

Go framework generating OpenAPI documentation from code. Inspired by Nest, built for Go developers.

In this post, we are going to have a look at

- What is a memory leak
- Why are memory leaks bad
- Common causes for memory leaks in Go
- Methods for identifying memory leaks
- Investigate memory leaks

Hatchet replaces difficult to manage legacy queues or pub/sub systems so you can design durable workloads that recover from failure and solve for problems like concurrency, fairness, and rate limiting. Instead of managing your own task queue or pub/sub system, you can use Hatchet to distribute your functions between a set of workers with minimal configuration or infrastructure.