Microsoft Azure has over 20 platform-as-a-service (PaaS) offerings that can act in support of a big data analytics solution. So which one is right for your project? This practical book helps you understand the breadth of Azure services by organizing them into a reference framework you can use when crafting your own big data analytics solution. Youíll not only be able to determine which service best fits the job, but also learn how to implement a complete solution that scales, provides human fault tolerance, and supports future needs. Understand the fundamental patterns of the data lake and lambda architecture Recognize the canonical steps in the analytics data pipeline and learn how to use Azure Data Factory to orchestrate them Implement data lakes and lambda architectures, using Azure Data Lake Store, Data Lake Analytics, HDInsight (including Spark), Stream Analytics, SQL Data Warehouse, and Event Hubs Understand where Azure Machine Learning fits into your analytics pipeline Gain experience using these services on real-world data that has real-world problems, with scenarios ranging from aviation to Internet of Things (IoT)
No es un libro para lograr la "Maestría" sino más bien es un libro para poder hacer SQL en diferentes servicios de Azure. El título podría ser "Cómo volver SQL toda aplicación analítica".
A good tour of Azure offerings across the analytics pipeline. Unfortunately, the worked example is heavily dependent on external sources that are already falling into the quicksand of obsolescence.
The book is ok explaining the concepts of data pipelines and the lambda/kappa architecture.
However, when it gets into practical exercices, I found it to be quite repetitive, having the same explaination over and over. Besides, going through so many technologies, the explanations given on each of them seemed either too detailed or too shallow.
I found myself skipping some chapters or skimming through them as they were a bit boring, only doing very basic analysis. Maybe I have a problem with Azure cloud which I find very "enterprise friendly" but not much "independent developer friendly" :)