Book Image

Practical Real-time Data Processing and Analytics

Book Image

Practical Real-time Data Processing and Analytics

Overview of this book

With the rise of Big Data, there is an increasing need to process large amounts of data continuously, with a shorter turnaround time. Real-time data processing involves continuous input, processing and output of data, with the condition that the time required for processing is as short as possible. This book covers the majority of the existing and evolving open source technology stack for real-time processing and analytics. You will get to know about all the real-time solution aspects, from the source to the presentation to persistence. Through this practical book, you’ll be equipped with a clear understanding of how to solve challenges on your own. We’ll cover topics such as how to set up components, basic executions, integrations, advanced use cases, alerts, and monitoring. You’ll be exposed to the popular tools used in real-time processing today such as Apache Spark, Apache Flink, and Storm. Finally, you will put your knowledge to practical use by implementing all of the techniques in the form of a practical, real-world use case. By the end of this book, you will have a solid understanding of all the aspects of real-time data processing and analytics, and will know how to deploy the solutions in production environments in the best possible manner.
Table of Contents (20 chapters)
Title Page
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Spark architecture - working inside the engine


We have looked at the components of spark framework, its advantages/disadvantages, and the scenarios where it best fits in solution design. In the following section, we will delve deeper into the internals of Spark, its architectural abstractions, and workings. Spark works in a master salve model and the following diagram shows the layered architecture for it:

If we start bottom up from the layered architecture depicted in the preceding diagram:

  • The physical machines or the nodes are abstracted by a data storage layer (that could a HDFS/distributed file system/AWS S3). This data storage layer provides the APIs for storage and retrieval of final/intermediate data sets generated during the execution.
  • The resource manager layer on top of the data storage obfuscates the underlying storage and resource orchestration from spark set up and execution model, thus providing the users a spark setup that could leverage any of the available resource managers...