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

Flink architecture and execution engine


Flink is a platform for distributed stream and batch data processing. The core of Flink is a streaming dataflow engine. Flink is based on Kappa architecture. Kappa architecture was introduced in 2014 by Jay Kreps in https://www.oreilly.com/ideas/questioning-the-lambda-architecture which addresses the pitfalls of Lambda architecture. So before going into the details of Flink, let's figure out the base of Flink: Kappa architecture. Kappa architecture is designed to handle real-time data processing and continuous data reprocessing using a single data stream. There were two main concerns raised related to Lambda architecture: maintaining two different code bases for real-time analytics and batch analytics on the same source data and the reprocessing of events will require code changes which is not easy to maintain as seen in the following figure:

So in Kappa architecture, there is everything in streaming data. In case of the failure and reprocessing of...