en
Feedback
CatOps

CatOps

Open in Telegram

DevOps and other issues by Yurii Rochniak (@grem1in) - SRE @ Preply && Maksym Vlasov (@MaxymVlasov) - Engineer @ Star. Opinions on our own. We do not post ads including event announcements. Please, do not bother us with such requests!

Show more
5 088
Subscribers
+124 hours
+57 days
+230 days
Attracting Subscribers
September '26
September '26
+32
in 0 channels
August '26
+44
in 0 channels
Get PRO
July '26
+77
in 0 channels
Get PRO
June '26
+59
in 0 channels
Get PRO
May '26
+61
in 1 channels
Get PRO
April '26
+43
in 0 channels
Get PRO
March '26
+57
in 1 channels
Get PRO
February '26
+38
in 0 channels
Get PRO
January '26
+40
in 0 channels
Get PRO
December '25
+63
in 1 channels
Get PRO
November '25
+79
in 1 channels
Get PRO
October '25
+45
in 1 channels
Get PRO
September '25
+19
in 1 channels
Get PRO
August '25
+27
in 0 channels
Get PRO
July '25
+72
in 0 channels
Get PRO
June '25
+16
in 0 channels
Get PRO
May '25
+26
in 0 channels
Get PRO
April '25
+30
in 1 channels
Get PRO
March '25
+63
in 2 channels
Get PRO
February '25
+45
in 0 channels
Get PRO
January '25
+75
in 1 channels
Get PRO
December '24
+63
in 0 channels
Get PRO
November '24
+70
in 1 channels
Get PRO
October '24
+73
in 1 channels
Get PRO
September '24
+55
in 0 channels
Get PRO
August '24
+139
in 3 channels
Get PRO
July '24
+56
in 3 channels
Get PRO
June '24
+126
in 0 channels
Get PRO
May '24
+157
in 0 channels
Get PRO
April '24
+305
in 1 channels
Get PRO
March '24
+232
in 1 channels
Get PRO
February '24
+299
in 3 channels
Get PRO
January '24
+297
in 0 channels
Get PRO
December '23
+246
in 1 channels
Get PRO
November '23
+89
in 2 channels
Get PRO
October '23
+85
in 2 channels
Get PRO
September '23
+133
in 0 channels
Get PRO
August '23
+351
in 0 channels
Get PRO
July '23
+339
in 0 channels
Get PRO
June '23
+330
in 0 channels
Get PRO
May '23
+320
in 0 channels
Get PRO
April '23
+233
in 0 channels
Get PRO
March '23
+807
in 0 channels
Get PRO
February '23
+226
in 0 channels
Get PRO
January '23
+208
in 0 channels
Get PRO
December '22
+128
in 0 channels
Get PRO
November '22
+53
in 0 channels
Get PRO
October '22
+76
in 0 channels
Get PRO
September '22
+149
in 0 channels
Get PRO
August '22
+64
in 0 channels
Get PRO
July '22
+94
in 0 channels
Get PRO
June '22
+219
in 0 channels
Get PRO
May '22
+49
in 0 channels
Get PRO
April '22
+27
in 0 channels
Get PRO
March '22
+469
in 0 channels
Get PRO
February '22
+90
in 0 channels
Get PRO
January '22
+97
in 0 channels
Get PRO
December '21
+57
in 0 channels
Get PRO
November '21
+48
in 0 channels
Get PRO
October '21
+69
in 0 channels
Get PRO
September '21
+76
in 0 channels
Get PRO
August '21
+94
in 0 channels
Get PRO
July '21
+40
in 0 channels
Get PRO
June '21
+55
in 0 channels
Get PRO
May '21
+63
in 0 channels
Get PRO
April '21
+57
in 0 channels
Get PRO
March '21
+61
in 0 channels
Get PRO
February '21
+80
in 0 channels
Get PRO
January '21
+56
in 0 channels
Get PRO
December '20
+4 510
in 0 channels
Date
Subscriber Growth
Mentions
Channels
16 September+3
15 September+3
14 September0
13 September+4
12 September+2
11 September+1
10 September0
09 September+1
08 September+3
07 September+2
06 September+1
05 September+2
04 September+1
03 September0
02 September+1
01 September+8
Channel Posts
Why Distributed Databases Fail at Coordination Boundaries is a neat article on the areas to pay attention to when working with any distributed system, really. #db

2
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
1 017
3
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
979
4
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
1 003
5
​​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
1 100
6
A new issue of the CatOps Digest is here! https://newsletter.catops.dev/p/catops-digest-2026-09-04 #digest #newsletter
1 163
7
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
1 212
8
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
1 112
9
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
1 063
10
​​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
998
11
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
1 333
12
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
1 275
13
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
1 216
14
​​Happy Independence Day of Ukraine! πŸ’›πŸ’™ It always starts with small steps, but every step counts. So today, I'd like to get back to small fundraisers that also matter! Here, a friend of mine is raising funds for a pickup track for the Zaporizhzhia direction. You can find more info in this Instagram post (in Ukrainian). You can donate to this Monobank jar: https://send.monobank.ua/jar/8Mjotj4Uei #donations #Ukraine
1 159
15
A new issue of the CatOps Digest is here! https://newsletter.catops.dev/p/catops-digest-2026-08-22 #newsletter #digest
1 239
16
​University of Colorado published an article about a study of 7700 employees that shows that Remote workers report the highest well-being. The study simply analyzed the self-reported data without any judgments on why exactly this is the case, but one of the authors points out that: The study did not explore why remote workers reported higher well-being, but Johnson points to a growing body of research on autonomy and flexibility. One explanation is that remote workers have greater control over their work setup and daily schedule, she said. "If you have control over your environment, you tend to have more positive outcomes," she said. Working from home can also eliminate many everyday stressors. "Spending a lot of time in traffic is negatively related to well-being," Johnson said. "There are so many little stressors associated with being in the office." Those stressors can include arranging child care, hiring help for pets or managing the logistics of getting to and from work, she said. Johnson said the study points to a broader lesson for employers navigating return-to-office debates. Rather than focusing only on where employees work, organizations may get better results by investing in employee well-being. I know that this has nothing to do with the immediate topic of systems / platform / reliability engineering, but I still find this article amusing, since we all are doing our jobs in one way or another: in an office or remotely. Now, you also have a study to point to, if anyone brings up the topic of the remote work and well-being. However, it's important to keep in mind that the employee well-being is not necessary the metric that is being optimized when the RTO directives are issued. #culture
1 290
17
A postmortem for the recent GitHub incident. Regarding the cause: The immediate cause of the failure was network saturation on load balancers in Central US due to a new peak in traffic. Originally this was caused by an Istio sidecar pod reaching its concurrency limits and failing to auto scale correctly because of a misconfigured policy that watched host service but not sidecar limits. One failure cascaded to more and eventually four HAProxy nodes exhausted their flow limits, degrading the gateway auth path and causing widespread authentication latency and failures. The problem was worsened by optimistic retry logic which overloaded internal load balancers. Pausing HAProxy on those nodes simultaneously produced immediate broad recovery. #postmortem #github
1 227
18
The Hidden Cost of Postgres Constraints at Scale is a description of a bottleneck foreign keys can create in a write-heavy PostgreSQL table. It also has recommendations of what you can do to overcome that. Now, I would say, it's a corner case for many people. The author works in a company that develops their own time series solution based on Postgres, so for them, it makes sense. For the vast majority of people, I would argue, it makes more sense to offload the integrity checks to the database, rather than trying to implement those in-house. Of course, it may be different for you, but no one knows your system better than you do. #db #postgres
1 240
19
Last Sunday we discussed that we all learn anew, how to deal with agentic SDLC. Here's a great interview with a principal engineer at Adyen and a former Amazonian Heitor Lessa on how he approaches this. The interview is long and information-dense at times, but it's worth the time! #ai #youtube
1 460
20
Argo For Kubernetes: From Argo CD to Workflows and Image Updater | A complete Guide is a nice article about building a complete CD workflow with Argo products in a home lab. I would still not call it a "complete guide", because it's only scoped for local development, but it's a nice entry point, if you want to learn more about Argo on a home server, or create a small PoC. #cicd #kubernetes #argo
1 376