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

RabbitMQ exchanges


RabbitMQ is versatile and provides for a variety of exchanges which are at the disposal of its developers to cater to a myriad of problems that come across for implementation.

Direct exchanges

In this type of exchange, we have a routing key bound to the queue, which serves as a pass key to direct the messages to the queue. So every message that is published to the exchange has a routing key associated with it, which decides the destination queue the exchange writes it to. For example, in the preceding figure, the message is written to the green queue because the message routing queue "green" binds to the green queue:

Fanout exchanges

They can also be called broadcast exchange, because when a message is published to a Fanout Exchange it's written/sent to all the queues bound to the exchange. The preceding figure demonstrates its working. Here the message published by the producer is sent to all the three queues; green, red, and orange. So in a nutshell each queue bound to the...