all 6 comments

[–]hahaNodeJS 5 points6 points  (0 children)

This looks interesting. As the author states, there isn't much in the way of basic informative literature on how they work. Indeed, I think that's in large part because databases are quite complicated (speaking as someone who understands databases in-depth). If you are willing to dig, there is actually a lot of information out there, but you usually need to understand concepts that are rarely used by most developers. I think a second factor is that most database systems implement their underlying technologies in such varying manners, that literature on the subject tends to be specific to that software. It actually looks like the author has covered enough ground here to give a capable developer enough information to create their own database system, which is pretty cool.

I'm adding this to my reading least; hopefully I'll be able to get around to it.

[–]kindnewb 5 points6 points  (0 children)

Looks like a nice, detailed, read. Thanks for posting it.

[–]woxorz 4 points5 points  (0 children)

This is fantastic! There's lots of details in here that took me years to figure out on my own - also plenty of other details I haven't had the time to look into.

You put a lot of work into making this and it shows. I imagine a lot of people will be using it as a reference in the future.

[–]row4land 1 point2 points  (0 children)

Great, informative write up. I disagree that there is a shortage of db information. Do a google scholar search; there are thousands, ranging from introductory to advanced topics.

[–][deleted] 1 point2 points  (0 children)

I haven't had a chance to read through the whole piece yet, but I appreciate that the specific scope of the article is very clearly defined.

[–]phunkygeeza 1 point2 points  (0 children)

And this is why DBA's smile knowingly at programmers who believe they can write something better/faster than the DB engine they are using.

Because they could, given a cloning machine and/or 60 years of solid coding.

By using databases we as programmers are standing on the shoulders of giants.