Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Data Lake for Enterprises

You're reading from  Data Lake for Enterprises

Product type Book
Published in May 2017
Publisher Packt
ISBN-13 9781787281349
Pages 596 pages
Edition 1st Edition
Languages
Authors (3):
Vivek Mishra Vivek Mishra
Profile icon Vivek Mishra
Tomcy John Tomcy John
Profile icon Tomcy John
Pankaj Misra Pankaj Misra
Profile icon Pankaj Misra
View More author details

Table of Contents (23) Chapters

Title Page
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
Part 1 - Overview
Part 2 - Technical Building blocks of Data Lake
Part 3 - Bringing It All Together
1. Introduction to Data 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

When not to use Kafka


For certain scenarios and use cases, you shouldn't use Kafka:

  • If you need to have your messages processed in order, you need to have one consumer and one partition. But this is not at all the way Kafka works and we do have multiple consumers and multiple partitions (by design one consumer consumes from one partition) and because of this, it won't serve the use case that we are looking to implement.
  • If you need to implement a task queue because of the same reason in the preceding point. It doesn't have all the bells and whistles that you associate with a typical queue service.
  • If you need a typical topic capability (first in first out) as the way it functions is quite different.
  • If your development and production environment is Windows or Node.js based (subjective point but it's good to know that this aspect is quite true).
  • If you need high security with finer controls. The original design of Kafka is not really created with security in mind and this plagues Kafka at times...
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 $15.99/month. Cancel anytime}