Live data from Hacker News

Things to know about databases

architecturenotes.co

11–20 of 247 posts

Re: Things to know about databases

#11
post #10

From the SERIALIZABLE explanation: “The database runs the queries one by one … It is essential to have some retry mechanism since queries can fail.” I know they’re trying to simplify, but this is confusing. If the first part is true, the second part can’t be. In reality the database does execute the queries concurrently, but will try to make it seem like they were done one by one. If it can’t manage that, a query wil…

I believe there was a caveat around this exact point later in the post. It was really tough striking a balance for people learning this for the first time and more knowledgeable audience without confusing them further.

I do appreciate the feedback and will look to add some more color here! Thank you!

Re: Things to know about databases

#12

Earlier quoted context omitted.

We have another couple of notes from a few companies like Temporal, Sentry, and Gadget.

Awesome. Looking forward to additional content. If possible, would be great to get Mark Brooker (Principal at AWS) to provide some notes on bridging the gap between CAP theorem and how AWS relaxes constraints for building out Elastic Block Storage (EBS). https://brooker.co.za/blog/2014/07/16/pacelc.html

I will definitely reach out! Thanks for the suggestion!

Re: Things to know about databases

#18
Some of the explanations are questionable: I think they were overly simplified, and while I applaud the goal, some things just aren't that simple.

I highly recommend reading https://jepsen.io/consistency and clicking on each model on the map. This is the best resource I found so far for understanding databases, especially distributed ones.

Re: Things to know about databases

#19
post #18

Some of the explanations are questionable: I think they were overly simplified, and while I applaud the goal, some things just aren't that simple. I highly recommend reading https://jepsen.io/consistency and clicking on each model on the map. This is the best resource I found so far for understanding databases, especially distributed ones.

I would love the feedback, what was questionable? striking the balance is tough. jepsen's content is great.
Post reply on HN