A great article about Postgres' MVCC, or rather, issues with MVCC and the ways other engines tried to mitigate those.

It has a neat comparison of the tradeoffs, strong and weak parts of different implementations. It also provides insights into how different DB engines work.

A quote:

... if someone tells you a database has solved multi-versioning, ask them the four questions: where do old versions live, which way do chains point, what do indexes point at, and who cleans up. Then ask what happens when a transaction stays open over lunch.

#postgres #databases

Cloudflare shares a story of how they automated GitHub issues triage with AI for their Astro project.

It neatly shows the evolution from a collection of skills to a semi(?) autonomous state machine that has taken the project to zero open issues.

They also share the workflows they use publicly, but in my opinion the more valuable lesson here is the step-by-step model of how they got there.

#ai #open_source

I've written an article about load testing of Apollo Router - a GraphQL API gateway.

It's mostly pictures, so it should be easy to follow :)

#graphql #load_test

​​For today's Donations Monday, I'd like to remind you about a fundraiser by a friend of mine. Its goal is to get 70k UAH for a pick up truck. So far, about 20k has been raised. Let's make it happen!

https://send.monobank.ua/jar/8Mjotj4Uei

#donations #Ukraine

I already shared postmortems from both OpenAI and Hugging Face on the recent security incident when a frontier model broke out of its sandbox to search for a solution for its task.

Here is a more detailed writeup by OpenAI on this incident. Given that OpenAI has an intrinsic motivation to advertise their models, I would still take this with a pinch of salt, but it should be interesting.

I haven't read this article fully yet, but the start is promising.

#ai #security

Continuing with the topic of AI.

A colleague of mine wrote an article on how to attribute the cost with AWS Bedrock with code samples of how to enable it and the description of pitfalls we encountered along the way.

#aws #ai #finops

A nice visualization of Go dependencies.

It's interesting how you can instantly see packages that support hundreds, if not thousands, of others. I would have guessed that testify is popular, but I wouldn't have guessed that it's the most popular.

Also, I did not expect to see Viper and Cobra being so influential, even though I think they are cool.

#go #programming

A new issue of the CatOps Digest is here!

https://newsletter.catops.dev/p/catops-digest-2026-09-04

#digest #newsletter

​​Today, I’d like to remind you about the fundraiser a friend of mine is doing. The goal is to raise 70k UAH for a pickup truck for Zaporizhzhia direction.

You can donate on this Monobank jar:

https://send.monobank.ua/jar/8Mjotj4Uei

#donations #Ukraine

An interesting article on how to configure AI reviews for Terraform plans with GitHub Actions and AWS Bedrock.

I don’t necessarily like the style of this article, but the content is cool. Now, I need to check how to do something similar with Atlantis. I presume, I could just trigger a GHA on a comment.

P.S. This article was brought to you by weekly.tf. If you actively work with Terraform, you may find this newsletter helpful. So, make sure to subscribe!

#terraform #ai

I recall, back in the day, there was a popular interview question: "What would you not automate in your job?" I haven't heard it for a while, but with AI now, maybe it's still relevant. Perhaps it's even more relevant than back then.

What SREs Should Automate — and Never Automate — with AI is an article about that. I would argue that the point about security incidents contradicts a bit to what was said earlier: if AI can collect the data for a normal incident, why cannot it do the same for the security one? A human would still stay in charge of the remediation and the final decision.

#sre #ai

I don’t remember, if I shared this book bundle with you, but it won’t hurt to share it again.

Think like a programmer by No Starch Press.

#books