Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
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

When to use Flink


Select Flink as your data processing technology when:

  • You need high performance. Flink at the moment is one of the best in performance for stream processing.
  • Your use case needs machine learning. Flink’s native closed loop iterations operators make the processing perform much faster.
  • Your use case needs graph processing. Again, because of the preceding same feature, Flink will process data faster.
  • You require high throughput rates with guaranteed consistency.
  • You need exactly one time processing. This also eliminates duplicate record processing.
  • You want to avoid handling memory manually and leave that to the framework. Flink has automatic memory management.
  • You need to deal with intermediate results and Flink follows the data flow approach making it easy to do this.
  • You need less configuration. Many aspects in Flink are abstracted away from the user and this makes configuration simple.
  • You need to deal with both batch and stream data using the same framework. Flink is a hybrid...
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 $19.99/month. Cancel anytime
Banner background image