20h ago · 6 min read · In previous article , we discussed lost updates and database locking, which focused on how data is written. In this article, we’ll focus on how data is read during a transaction using isolation levels
Join discussion10h ago · 9 min read · For a while, I thought channels were Go's way of doing message passing. Something like Erlang processes or actors, except with a simpler syntax. That understanding is fine if you're writing tutorials. It is not fine when you've just OOM-killed a pod ...
Join discussion20h ago · 5 min read · Everything was working fine until two users try to book same seat at the same time. I was working on backend of my event ticket booking system project. It’s a simple system where users can register, s
Join discussion
2d ago · 10 min read · In the journey of creating a new programming language, there's a moment when the focus shifts from parsing syntax and generating code to breathing life into the runtime. For any modern language aspiring to relevance, this inevitably means tackling co...
Join discussion3d ago · 39 min read · TLDR: A lost update occurs when two concurrent read-modify-write transactions both read the same committed value, both compute a new value from it, and both write back — with the second write silently discarding the first. No error is raised. Both tr...
Join discussion
3d ago · 30 min read · TLDR: A dirty write occurs when Transaction B overwrites data that Transaction A has written but not yet committed. The result is not a rollback or an error — it is silently inconsistent committed data: one table reflects Transaction B's intent, anot...
Join discussion
5d ago · 12 min read · Introduction I was working on a service that accepts a large file over HTTP, validates it, encrypts it, uploads it to cloud storage, parses it, processes the records, and stores the results. Nothing e
Join discussion
