Fast Data Architectures for Streaming Applications

by Dean Wampler

Genres: Nonfiction, Technology

45 pages, ebook

Published August 31, 2016

Reviews

[Ahmad hosseini · Rating 4 out of 5]

Book explains most important topics in fast data architecture and I think it’s excellent for start point.

[Joe · Rating 1 out of 5]

This isn't so much a book as a management-style slide presentation puffed up with interstitial text. From a technical standpoint it is content-free.

[chalda · Rating 4 out of 5]

Short summary what are technologies used in stream application architecture. Cohesive showcase of difference between batch processing and stream processing. Of course there is emphasis on usage of Akka as book is written from Lightbend. Overall interesting.

[Ivan Orone · Rating 4 out of 5]

A very good summary if you are in the process of deciding which streaming tools to use.

If completely new to the streaming world, I would encourage one to first read "Making Sense of Stream Processing" by Martin Kleppmann and then reading this book next to make a decision on what to choose.

[Stefana Dranca · Rating 4 out of 5]

Great starting point for someone who doesn’t know much about batch and streaming architectures as it gives an overview of the technologies you can use in each case and how and it doesn’t go too deep in detail (although this can also be regarded as a downside).

[Alex · Rating 5 out of 5]

A very good introduction into the topic.

[David Stevenson · Rating 4 out of 5]

A nice short introduction.

[Marcelo Lopes · Rating 4 out of 5]

Muito bom.

[Helen Mary · Rating 3 out of 5]

It’s a decent high level overview for people new to streaming data architectures. If you need the nuts and bolts for tech implementations, other longer and newer references may be more suitable.

[Johnny · Rating 1 out of 5]

Small but disappointing. There are many good chances in the book that could lead to a helpful handbook. However, nearly none of them is used. The title is about architectures (plural), while the book only covers one architecture in detail. I doubt the usefulness of explaining the technical parts while not covering (enough) the interactions between them. Could you drive a car when I explain you that this big thing in the front is an engine, the round thing at the side is called a wheel and that little switch here opens your windows? Probably not.

It would be much better when this book would focus on the analytics part and only show you a diagram of a possible architecture. What is there now does neither in a satisfying manner.