Bitesized Engineering
It’s Saturday and what a better way to spend 3 mins of your weekend than by refreshing your knowledge on DB’s Transaction Isolation Levels, right? RIGHT? 🤓
I know, I know, who cares about that? It’s a boring and hard-to-grasp topic. And you have your fancy ORM that does it for you anyway … Which all makes sense until you learn that there are some weird scenarios like “Lost Updates” and “Dirty Reads”. Ouch!
“Well, no problem”, you say, “I’ll just tighten my Transaction Isolation Level. I don’t even need to understand how that works, because the higher the better”. And that’s true - higher isolation level is better; until you see the performance hit :)
Here’s what I want to do - I want to give you a frame in which to think about DB Transaction Isolation levels, but through lens of something that you can easily remember. Through the lens of Building a Snowman :)
I hope that was amusing enough :) Because, Isolation levels are actually really cool concepts to grasp. They do have their own set of intricacies, but, for starters, you should at least be aware on what they are.
