Once, when I picked up a book from the local library, the librarian asked to tell her what I thought about the book when I would bring it back. Well, why not write a few lines about all the books I read so everybody could see what I thought about it? I'm often also happy to have friends recommend a certain book or tell me this and that is not really worth reading. I won't comment about the tons of books I have read so far, but about books I read from now on.
highly recommended | sehr empfohlen | |
good reading | gutes lesematerial | |
average | durchschnittlich | |
not too interesting | nicht allzu interessant | |
recommended not to read it | empfehlung das buch nicht zu lesen |
![]() |
|
---|---|
title | I ♥ Logs |
author | Jay Kreps |
ISBN-10 | 1-491-90938-2 |
ISBN-13 | 978-1-491-90938-6 |
ASIN | |
rating | |
date | 2020-Jan-25 |
How you perceive this book probably depends on what you consider to be a 'log'. As a guy having spent the last 7 years running a company-wide log-analysis system, I find the notion of 'log' in this book rather narrow-minded. What Kreps writes about clearly is 'transaction logs' and 'message queues'. So unless this is exactly what you are looking for, it is probably not the book you're interested in. It also clearly shines through that Kreps is a big fan of Kafka.
Even though the author claims to have lots of experience with designing systems around (transaction) logs at LinkedIn, he never gives any technical advice or hard facts on how to interconnect various systems, not even on how to structure the messages you are passing between the systems. Working more than 25 years in IT building various company-wide systems and services myself, I have read dozens of books published by O'Reilly and have come to appreciate this publisher for their high quality technical books. This book definitely does not even come close to the standard I have come to expect from O'Reilly. I ♥ Logs is more suited to a blog post or one of the cheap write-ups found with some other publishers.