Earlier quoted context omitted.
I'm currently writing a book for PragProg called Building Distributed Services with Go (though it mostly applies to other languages too) that's walks you through building a distributed database from scratch. You can sign up on this mailing list to know when it's available: https://travisjeffery.us4.list-manage.com/subscribe?u=1e3ff7...
Do you have an experience or learning along writing? (also a legit/common way)
Database Internals
31–39 of 39 posts
Re: Database Internals
#32Earlier quoted context omitted.
Awesome. Just signed up. Any ideas on what the pricing will be like?
Not sure, haven't gotten to that yet. Just from looking at the prices of other PragProg books somewhere around $21.95-24.95.
Re: Database Internals
#33I also recommend following Andy Pavlo and the CMU Database Group which has lots of free courses, videos and material: https://db.cs.cmu.edu/ https://www.youtube.com/channel/UCHnBsf2rH-K7pn09rb3qvkA
It suffers from the common issue for such content - theory/lectures are too diverged from the practical/lab part.
Re: Database Internals
#34Here's the landing page for the book's implementation: http://www.cs.bc.edu/~sciore/simpledb/intro.html
Unfortunately, I don't think the book is in print anymore.
Re: Database Internals
#35Earlier quoted context omitted.
Not sure, haven't gotten to that yet. Just from looking at the prices of other PragProg books somewhere around $21.95-24.95.
Is it still worth (materialistically) writing a book considering (see PRICING section) http://fabiensanglard.net/gebbdoom/ ?
Re: Database Internals
#36I also recommend following Andy Pavlo and the CMU Database Group which has lots of free courses, videos and material: https://db.cs.cmu.edu/ https://www.youtube.com/channel/UCHnBsf2rH-K7pn09rb3qvkA
It suffers from the common issue for such content - theory/lectures are too diverged from the practical/lab part.
There are tons of open-source databases on github that you can hack on so I don't think there's a major issue with getting practical experience if you want it.
Re: Database Internals
#37Earlier quoted context omitted.
Preferring one font over the other is more a question of taste, but I think you're right about font-weight: it does read better with 400. Thanks for the tip!
And thank you for being so responsive to feedback! It's much easier to read now. I also want to apologize for my comment being a little grouchy; I should know better than to comment on style and readability in the wee hours. :-)
Re: Database Internals
#38In past few days I've heard so many praises and also I have heard so much criticism about Database Books in general. What makes this book so much better?
It depends on your goal. Database internals books are not worth reading if you want to work on implementing real world database engines. You are better off checking out internals and documentation of various implementations and also research papers in that field. And you would be doing your own research anyway. But if you are just starting out in programming, it's probably as good book as any to learn something new a…
Some of the folks I talked to who have already worked with databases a lot mentioned they've benefited from the book as well, since there were some concepts they were less familiar with or never had to learn (for example, transactional processing for the folks who have mostly worked with on eventually consistent databases; or B-Tree details for the folks who have mostly worked on LSM-Based storage engine)
Disclaimer: I'm author of this book.
Re: Database Internals
#39Earlier quoted context omitted.
Is it still worth (materialistically) writing a book considering (see PRICING section) http://fabiensanglard.net/gebbdoom/ ?
I'm not doing it for the money. Writing a worthwhile book is about the least efficient way to make money.