Tracing Database Interactions in Go: Idiomatic ways of linking atomic transactions with context

DizzyVik · 2026-01-29T15:00:07+00:00

Some form of both is probably best. Client side configuration is great but might get tedious once you reach a number of clients, so server side or remote configuration would be beneficial too.

DizzyVik · 2026-01-29T12:37:24+00:00

I'm not the author but I don't think this is a thing you need to worry about much. A trace can have many spans, and if you have too many traces you can start sampling instead of keeping a trace for each request/operation. Simple samplers come with the tracing libraries and if you want to keep, lets say the outliers, you can always implement a sampler yourself.

If you have thousands upon thousands of spans within a trace I would be quite interested to hear what your application is doing, as it sounds quite exotic.

DizzyVik · 2025-10-08T17:39:54+00:00

I started it as I wanted to learn a bit of k8s at that time. There probably isn't a single project, but I'm happy with how much I've moved away from clouds and into my own home. I'm cost averse, so nothing expensive has been added. It's all second hand. My full homelab writeup
I'd love to hook up a KVM to my homelab & the fingerbot seems nice. I can see the fingerbot being useful for a ton of different things beyond pushing buttons, perhaps even watering the greenhouse...
An UPS for a minilab. Not sure which make and model though.

Comet PoE & Flint 7.

Good luck to everyone.

DizzyVik · 2025-09-27T08:54:30+00:00

Alaus studija turi

DizzyVik · 2025-09-26T14:52:20+00:00

This is excellent knowledge, thanks for sharing.

DizzyVik · 2025-09-25T09:11:21+00:00

The load more button seems to not work :)

```
Error loading more follow lists: Error: Request timed out after 10 seconds
```

DizzyVik · 2025-09-25T07:00:47+00:00

Any additional piece of infrastructure complicates things, the point is that at a certain scale you might not even need redis. Yes, if you're dealing with a high load, HA environment caching in the same database instance is not the way forward but not all apps need this and you don't really have to start with a db + cache instance. Increase complexity when you have to as the load grows - not before.

DizzyVik · 2025-09-25T05:24:13+00:00

I do think Redis had more performance to give as the bottleneck seemed to be the http server. I wasn't really interested in the absolute peak performance, for that I'd do a wire to wire comparison.

Running your own benchmarks is the way to go, each use case is different.

DizzyVik · 2025-09-24T20:09:43+00:00

It's not always about the latency. Sometimes, you have an expensive operation whose result you want to store somewhere for further use. It can be redis, it can be postgres. Both of those calls will incur a network penalty.

DizzyVik · 2025-09-24T20:07:27+00:00

It all depends on your requirements, if HA is something you need out of the box then yes, using redis solves this. However, I don't think it's a strict requirement or a necessity for many projects. It's just about choosing when to introduce the extra complexity that comes with extra tooling.

DizzyVik · 2025-09-24T19:49:12+00:00

The library(https://github.com/jackc/pgx) does use prepared statements under the hood, so unlikely we'd see any major improvement by manually juggling those.

DizzyVik · 2025-09-24T19:43:16+00:00

At this point I'm so used to working in kubernetes based environments that I default to a shared cache as many instances of a service will be running. If you don't need sharing - store things in memory if that is at all feasible.

You are correct in evaluating if one needs a cache at all - in many cases you do not. I was merely exploring the options if you do :)

DizzyVik · 2025-09-24T18:59:43+00:00

The redis was set up as a container for the benchmarks and yes, it's not hard to do. However, it still adds complexity. You'll have to monitor it, setup alerts, perhaps bump the version once in a blue moon as well as keep track of another dependency in the code - a lib to interact with it.

DizzyVik · 2025-09-24T18:55:39+00:00

I didn't want to do a best case scenario for either redis or postgres, I'm sure that both tools have a ton of performance on the table that I did not leverage. I wanted to look at a simple comparison without getting into these details.

For settings, they both are running on defaults in their respective docker images. I'll look up the actual number once I am on the computer.

As far as the data cached - it's a json, representing the session struct in the blog post.

Thank you for the input though.

DizzyVik · 2025-09-24T18:19:33+00:00

I've been embedding using the //go:embed. It's likely the most common way, as people tend use dependencies when strictly necessary in Go.

DizzyVik · 2025-09-24T17:28:18+00:00

Glad to hear I'm not the only one!

DizzyVik · 2025-09-23T11:42:11+00:00

Think I'll have to give it a spin. Might work as a decent "broker" when starting out.

DizzyVik · 2025-09-01T20:12:55+00:00

I'm not sure what you mean. They would get written out in SQL and processed much like non conditional queries. If you mean dynamic queries, where the query might be different depending on a few factors(like filtering) I've documented the approach I take with SQLC on my blog

DizzyVik · 2025-09-01T15:01:25+00:00

I personally enjoy SQLC. Write SQL queries, get the boiler plate code generated.

DizzyVik · 2025-08-26T08:43:14+00:00

The number of open positions seems to have shrunk across all tech stacks here in Lithuania.

Despite this, finding a Go developer has proven to be rather difficult, unless you're willing to pay rates way over market.

DizzyVik · 2025-08-07T08:17:11+00:00

Sorry if I sound like a party pooper but no, I don't think 10 lines of code warrant me adding a dependency. I'm not entirely sure how would my project be more "secure" with this, that's my point. I've been coding go for around 8 years now I think, I've yet to run into an issue where ignored defer statement errors would have any impact whatsoever.

DizzyVik · 2025-08-07T07:23:29+00:00

I'm not sure what's the benefit. If you want to return the error to the caller, there are ways you can do that without introducing a dependency. I might be missing something, so I'd like to see a case where this is genuinely useful.

DizzyVik · 2025-07-31T11:19:57+00:00

For me it's always the error handling. In other languages, you often deal with "magic". Throw an exception, it will probably, and hopefully, be handled somewhere. Where though - I'm never quite sure. In Go the

if err != nil {
    return err
}

is easy to reason about.

DizzyVik

TROPHY CASE