- Taschenbuch: 195 Seiten
- Verlag: Manning; Auflage: Pap/Psc (22. Juni 2017)
- Sprache: Englisch
- ISBN-10: 1617292281
- ISBN-13: 978-1617292286
- Größe und/oder Gewicht: 18,5 x 1 x 23,4 cm
- Durchschnittliche Kundenbewertung: Schreiben Sie die erste Bewertung
- Amazon Bestseller-Rang: Nr. 136.809 in Fremdsprachige Bücher (Siehe Top 100 in Fremdsprachige Bücher)
Andere Verkäufer auf Amazon
+ EUR 3,00 Versandkosten
Streaming Data (Englisch) Taschenbuch – 22. Juni 2017
|Neu ab||Gebraucht ab|
Kunden, die diesen Artikel gekauft haben, kauften auch
Welche anderen Artikel kaufen Kunden, nachdem sie diesen Artikel angesehen haben?
Es wird kein Kindle Gerät benötigt. Laden Sie eine der kostenlosen Kindle Apps herunter und beginnen Sie, Kindle-Bücher auf Ihrem Smartphone, Tablet und Computer zu lesen.
Geben Sie Ihre Mobiltelefonnummer ein, um die kostenfreie App zu beziehen.
Wenn Sie dieses Produkt verkaufen, möchten Sie über Seller Support Updates vorschlagen?
Über den Autor und weitere Mitwirkende
Andrew Psaltis is a software engineer and architect focused full time on building massively scalable real-time analytics systems using Spark, Kafka, Storm, Hadoop, and WebSockets.
|5 Sterne (0%)|
|4 Sterne (0%)|
|3 Sterne (0%)|
|2 Sterne (0%)|
|1 Stern (0%)|
Die hilfreichsten Kundenrezensionen auf Amazon.com
Book is very good starter book for the topic. It is only 216 pages. It shows different perspectives and what we encounter in real life designing data stream digesting analyzing application. Based on example it presents architecture of streaming pipeline. Informs what can be encountered during whole process in positive situation or when we are in trouble because one of our components went down and how prepare our architecture in any case of failure. Author shortly compares different solutions like for e.g. Spark, Storm, Kafka, Flink, shows briefly their pros and cons and what is missing to use certain tool. The same about different databases and in-memory caches. Helps to distinguish between technologies showing their pros and cons. Also explains algorithms which can be used when data are need to be analysed Bloom filter, HyperLogLog and Count-Min Sketch.
All in all the book should be valuable for people who are interested in architecture, o they want to improve their understanding or maybe existing approach.
The big plus is a lot of references to external sources either books or articles with links. I found the book to be helpful.
The disadvantage is that I would gladly find much more about reactive systems and sometimes content more clearly written.
However I can recommend a book and find it very positive.
Another great feature of this book, published by Manning, is that is comes with the e-book digital version at no extra cost. I wish all physical books followed this model. There is a small page inside the front cover that you cut open neatly with scissors. Inside is a matrix of codes. You must create an account on the Manning site, and then enter a few of these codes, and the download is made available. Several formats are available for download, including PDF and MOBI (for Kindle).
I downloaded the MOBI file and then used the "send to Kindle" document feature to deliver to my Kindle via email. It worked great, the front cover is used as the thumbnail and all hyper-linked, such as the table of contents, are active. The one thing I couldn't figure out was how to add this e-book to a collection on the Kindle or how to have it show up as a book instead of a document. I googled for answers, tried moving the file into a /book directory, and ultimately could not figure it out. But the e-book version is much appreciated nonetheless.
If you have an interest, and particularly if you work in this industry, you will benefit from absorbing this information. From introduction, data ingestion, decoupling the pipeline, analysis, algorithms, storage, availability, and device limitations - this book has it all in a very concise but complete format. There are many visual diagrams and charts that help explain the concepts throughout. Highly recommended.
I'm tech savvy but I don't really work with hardware, so sections of this book were outside of my wheelhouse and what I was interested in, although it was illuminating to read about the way that the hardware impacts performance and having that knowledge is probably something I'll use at some point in the future.
Overall, I found the discussion in this book somewhat on the shallow side which was perfect for me as a data user but might not have enough depth for others (if I were going into server management, this wouldn't cut it). The level of technical sophistication in the book was good -- it's clearly written for a tech-savvy crowd, but if you're not the kind of person who has exposure to technical documents and network maps, etc., this might be a bit on the jargony side.