Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Data Lake for Enterprises

You're reading from   Data Lake for Enterprises Lambda Architecture for building enterprise data systems

Arrow left icon
Product type Paperback
Published in May 2017
Publisher Packt
ISBN-13 9781787281349
Length 596 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Authors (3):
Arrow left icon
Pankaj Misra Pankaj Misra
Author Profile Icon Pankaj Misra
Pankaj Misra
Tomcy John Tomcy John
Author Profile Icon Tomcy John
Tomcy John
Vivek Mishra Vivek Mishra
Author Profile Icon Vivek Mishra
Vivek Mishra
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Introduction to Data FREE CHAPTER 2. Comprehensive Concepts of a Data Lake 3. Lambda Architecture as a Pattern for Data Lake 4. Applied Lambda for Data Lake 5. Data Acquisition of Batch Data using Apache Sqoop 6. Data Acquisition of Stream Data using Apache Flume 7. Messaging Layer using Apache Kafka 8. Data Processing using Apache Flink 9. Data Store Using Apache Hadoop 10. Indexed Data Store using Elasticsearch 11. Data Lake Components Working Together 12. Data Lake Use Case Suggestions

Producer and consumer reliability


In distributed systems, components fail. Its a common practice to design your code to take care of these failures in a seamless fashion (fault-tolerant).

One of the ways by which Kafka tolerates failure is by maintaining the replication of messages. Messages are replicated in so called partitions and Kafka automatically elects one partition as leader and other follower partitions just replicate the leader. The leader also maintains a list of replicas which are in sync so as to make sure that ideal replication is maintained to handle failures.

The producer sends message to the topic (Kafka broker in Kafka cluster) and durability can be configured using the producer configuration, request.required.acks, which has the following values:

  • 0: message written to network/buffer
  • 1: message written directly to partition leader
  • all: producer gets an acknowledgement when all in-sync replicas (ISR’s) get the message

Consumer reads data from topics and in Kafka the state of...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime