Streaming Systems: The What, Where, When, and How of Large-Scale Data Processing

Just could not put down the book until I finished it...I've built Big Data analysis systems for years, using Hadoop MapReduce on HBase, at the same time, we build Streaming System using Apache Storm(something following the Lambda Architecture pattern), and further extend to Trident to ensure exactly-once data processing. Later we moved to Spark so that we can use one implementation to do both batch and streaming... I'm so interested in streaming systems that I've also learned Flink and Akka Streaming in my own private time, and I feel I'm an expert for streaming systems or big data analysis systems, until I read this Book... I really know nothing...This Book lead you a way to jump out of the details, it shall build a framework in higher concept level in your mind, for you to understand and reasoning for streaming system, SQL system, and batch processing systems; and then you will find the essential same/difference between batch/Stream/table/SQL...etc, and understand those things which seem to locate in totally different dimensions, by only one simple mental framework; and then, you will find you can think in a higher level dimension space and attack your problem with a dimension reduction weapon, and it's really cool.It will change your mind on "what is big data processing".

What did you like or dislike? Familiar with lambda, unfamiliar to streaming, this book has some very good concepts that expanded the prior knowledge of batch programming!What did you use this product for? Learning/Expanding purposes

I almost finished part I of the book and I'm quite disappointed.After every chapter I thought "well, I didn't really enjoy this one, but next one surely will be better?" and it just never happened.The book is written by 3 authors, 1 of which uses the prose language as if he is writing a novel. I really dislike this writing style, I just want to understand the streaming systems better. Please use your eloquent language for other purposes, but not for tech writing.Overly simple concepts are explained in an overly complex language. I don't want to copy book contents here, but I will show the level of examples given in the book. If mobile phones generate events with numbers 1, 2, 3, 4 then they can arrive to our pipeline in any order, and - CAN YOU BELIEVE THAT?? - they always sum to 10.Really? That's just obvious and you don't have to make up complex terminology to explain this simple thing. Please rather explain to us how to deal with data that can not arrive from the phone, or how to estimate lateness of that data.The charts are really confusing. The X-axis for some reason is event-time (in my opinion, it would have been much easier to understand if processing time is put as an X-axis instead; author even mentions that there was similar feedback from other people but they just don't feel it's worth updating that!!!) - and to make things more complicated X-axis and Y-axis start at different times. So what should be a 0-crossing diagonal becomes a diagonal shifted on X-axis. I just loose my mental processing power adjusting the charts to the way they should have been printed to start with - and at that point I have very little capacity to reason about what is actually going on in the provided example.I feel I learned very little new things from this book, if any at all.I have prior experience working with streaming systems - and I guess that made me understand something written in this book, but otherwise I doubt I would be able to understand much.If part II enlightens me I will go back and change this review, but so far it's just a disappointment and waste of time.

The content in this book is good, but the formatting makes it very painful to read. There are many charts that are printed tiny with dotted lines and the reader is expected to type in a URL to view them online. Why not just print them bigger instead of packing 6 to 8 of them on one page? My other gripe is the use of yellow font color on white background. It's extremely difficult to read, as is the orange text with yellow highlight background color. I have mild color deficiency which doesn't help either, but come on guys, there are plenty of darker colors than yellow that could have be used.

On top of everything you learn about streaming data systems it was so much fun getting into how modern systems evolved and where some of the ideas came from

Very educational on the engineering fundamentals of streaming systems.

A+

The author likes to use phrases and sentences which are difficult to read and comprehend to explain simple concepts. Streaming systems is not some advanced algorithms which takes efforts to understand.On the other hand, it's pretty common nowadays that people tend to exaggerate the complexity of their work in the software engineering domain. Most of times I finish reading some book or articles with a "Meh" rather than "Woah".

La calidad de la impresión del libro es lamentable.Dicho esto, el contenido es de primer nivel.

Having read Tyler's famous Streaming 101/102 blog posts and having watched his presentations on youtube, I did not think I would get much out of this book. I was wrong. Tyler is the Edgar F. Codd of streaming systems.

DO NOT BUY. This is not a review of the book but the print that CB-India is selling. It is misprinted. Most of the book is typescript and not streaming systems. I have been trying to return the book but Amazon has been canceling the return. So very corrupt!

Me ha llegado hoy el libro, puedo decir que la edición del libro es de muy baja calidad para su precio. Por 50 euros espero hojas plastificadas y gráficas definidas. Como se ve en las imágenes las gráficas están borrosas. Parece un pdf impreso con muy poca definición. Si el libro tuviera un valor de 20 euros lo entendería.

From Page 33 onwards, the pages are from a different book. They actually talk about javascript and typescript.Even it's different from index. Need to return the book.