[Backend #9] Understand isolation levels & read phenomena in MySQL & PostgreSQL via examples

When working with database transactions, one crucial thing we must do is choosing the appropriate isolation level for our application. Although there’s a well-defined standard, each database engine might choose to implement it in a different way, and thus may behave differently in each isolation level. In this video, we will explore deeply how each level of isolation work in MySQL and Postgres by running some concrete SQL queries. It also shows you how each isolation level prevents read phenomena like dirty read, non-repeatable read, phantom read, and serialization anomaly.
- Join us on Discord: https://bit.ly/techschooldc
- Get the course on Udemy: https://bit.ly/backendudemy
- Buy us a coffee: https://www.buymeacoffee.com/techschool
- Full series playlist: https://bit.ly/backendmaster
- Github repository: https://github.com/techschool/simplebank
- Read it on DEV: https://dev.to/techschoolguru/underst...

Official documentation about transaction isolation levels:
- MySQL: https://dev.mysql.com/doc/refman/8.0/...
- Postgres: https://www.postgresql.org/docs/curre...

---

In this backend master class, we’re going to learn everything about how to design, develop, and deploy a complete backend system from scratch using PostgreSQL, Golang and Docker.

TECH SCHOOL - From noob to pro
   / techschoolguru  
At Tech School, we believe that everyone deserves a good and free education. We create high-quality courses and tutorials in Information Technology. If you like the videos, please feel free to share and subscribe to support the channel or buy us a coffee: https://www.buymeacoffee.com/techschool