Commit
0ec267e
wanted to read it for a while now but it seems the concepts discussed are too far off for me. do you think it helps in your day to day (some context about the scale you build for might help)
It helps to understand the differences in different databases. Basically, it explains in depth why ACID is a thing. I had one really nasty bug early in my career, where the app would write to a database, successfully apparently. But shortly after it would fail to read that same row. Of course when we checked manually during debugging process, the data would be there as expected. We all went WTF. Turns out, because the database we relied on switched to have replication, it hadn't fully finished writing by the time the app tried to read the same data. This book explains why not all databases are ACID (who needs a database that doesn't guarantee a write?!) and the tradeoffs.
If you ever have a managed database, which most people do, this book is a must read.
commit 0ec267e