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
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

Working of Hadoop


Let's now see the internals of Hadoop and its components, it's architecture, and how it works in this section. We will start off by understanding some of Hadoop’s core architecture principles, and then we will explain its architecture and important components in detail.

Hadoop core architecture principles

Hadoop was built and conceived with well-defined architecture goals and principles, as listed here, (the following are in no way authoritative as we can't find one; rather we gathered this from https://goo.gl/3nvERl):

  • Linear scalability (Scale-Out rather than Scale-Up): Add more nodes for scalability to increase data storage and computing power.
  • Bring code to data rather than data to code: In big data, data is usually huge and code working on data is small. So, this principle states that bring or distribute code to the nodes/machines where it can act on data and not distribute or move data. In essence, it means minimize data transfer and distribute code instead.
  • Deal with failures...
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