Adding Big Data module

courses/big_data/architecture.md

@@ -0,0 +1,76 @@
+# Architecture of Hadoop
+
+1. **HDFS**
+    1. The Hadoop Distributed File System (HDFS) is a distributed file system designed to run on commodity hardware. It has many similarities with existing distributed file systems. However, the differences from other distributed file systems are significant. 
+    2. HDFS is highly fault-tolerant and is designed to be deployed on low-cost hardware. HDFS provides high throughput access to application data and is suitable for applications that have large data sets. 
+    3. HDFS is part of the Apache Hadoop Core project.
+
+    ![HDFS Architecture](images/hdfs_architecture.png)
+
+        1. **NameNode:** is the arbitrator and central repository of file namespace in the cluster. The NameNode executes the operations such as opening, closing, and renaming files and directories.
+        2. **DataNode:** manages the storage attached to the node on which it runs. It is responsible for serving all the read and write requests. It performs operations on instructions on NameNode such as creation, deletion, and replications of blocks.
+        3. **Client:** Responsible for getting the required metadata from the namenode and then communicating with the datanodes for reads and writes.
+
+2. **YARN**
+    1. YARN stands for “Yet Another Resource Negotiator“. It was introduced in Hadoop 2.0 to remove the bottleneck on Job Tracker which was present in Hadoop 1.0. YARN was described as a “Redesigned Resource Manager” at the time of its launching, but it has now evolved to be known as a large-scale distributed operating system used for Big Data processing.
+    2. The main components of YARN architecture include: \
+
+    ![YARN Architecture](images/yarn_architecture.gif)
+
+        1. **Client:** It submits map-reduce jobs to the resource manager.
+        2. **Resource Manager:** It is the master daemon of YARN and is responsible for resource assignment and management among all the applications. Whenever it receives a processing request, it forwards it to the corresponding node manager and allocates resources for the completion of the request accordingly. It has two major components:
+        3. **Scheduler:** It performs scheduling based on the allocated application and available resources. It is a pure scheduler, which means that it does not perform other tasks such as monitoring or tracking and does not guarantee a restart if a task fails. The YARN scheduler supports plugins such as Capacity Scheduler and Fair Scheduler to partition the cluster resources.
+        4. **Application manager:** It is responsible for accepting the application and negotiating the first container from the resource manager. It also restarts the Application Manager container if a task fails.
+        5. **Node Manager:** It takes care of individual nodes on the Hadoop cluster and manages application and workflow and that particular node. Its primary job is to keep-up with the Node Manager. It monitors resource usage, performs log management and also kills a container based on directions from the resource manager. It is also responsible for creating the container process and starting it on the request of the Application master.
+        6. **Application Master:** An application is a single job submitted to a framework. The application manager is responsible for negotiating resources with the resource manager, tracking the status and monitoring progress of a single application. The application master requests the container from the node manager by sending a Container Launch Context(CLC) which includes everything an application needs to run. Once the application is started, it sends the health report to the resource manager from time-to-time.
+        7. **Container:** It is a collection of physical resources such as RAM, CPU cores and disk on a single node. The containers are invoked by Container Launch Context(CLC) which is a record that contains information such as environment variables, security tokens, dependencies etc. \
+
+
+# MapReduce framework
+
+![MapReduce Framework](images/map_reduce.jpg)
+
+    1. The term MapReduce represents two separate and distinct tasks Hadoop programs perform-Map Job and Reduce Job. Map jobs take data sets as input and process them to produce key value pairs. Reduce job takes the output of the Map job i.e. the key value pairs and aggregates them to produce desired results. 
+    2. Hadoop MapReduce (Hadoop Map/Reduce) is a software framework for distributed processing of large data sets on computing clusters. Mapreduce helps to  split the input data set into a number of parts and run a program on all data parts parallel at once.
+    3. Please find the below Word count example demonstrating the usage of MapReduce framework: \
+
+![Word Count Example](images/mapreduce_example.jpg)
+
+# Other tooling around hadoop
+
+1. **Hive**
+    1. Uses a language called HQL which is very SQL like.  Gives non-programmers the ability to query and analyze data in Hadoop.  Is basically an abstraction layer on top of map-reduce.
+    2. Ex. HQL query: 
+        1. _SELECT pet.name, comment FROM pet JOIN event ON  (pet.name = event.name);_
+    3. In mysql: 
+        2. _SELECT pet.name, comment FROM pet, event WHERE  pet.name = event.name;_
+2. **Pig**
+    1. Uses a scripting language called Pig Latin, which is more workflow driven.  Don't need to be an expert Java programmer but need a few coding skills.  Is also an abstraction layer on top of map-reduce.
+    2. Here is a quick question for you:
+    What is the output of running the pig queries in the right column against the data present in the left column in the below image? \
+
+    ![Pig Example](images/pig_example.png)
+
+    Output:
+    ```mysql
+    7,Komal,Nayak,24,9848022334,trivendram
+    8,Bharathi,Nambiayar,24,9848022333,Chennai
+    5,Trupthi,Mohanthy,23,9848022336,Bhuwaneshwar
+    6,Archana,Mishra,23,9848022335,Chennai
+    ```
+3. **Spark**
+    1. Spark provides primitives for in-memory cluster computing that allows user programs to load data into a cluster’s memory and query it repeatedly, making it well suited to machine learning algorithms.
+4. **Presto**
+    1. Presto is a high performance, distributed SQL query engine for Big Data. 
+    2. Its architecture allows users to query a variety of data sources such as Hadoop, AWS S3, Alluxio, MySQL, Cassandra, Kafka, and MongoDB.
+    3. Example presto query:
+        1. use studentDB;
+        2. show tables;
+        3. SELECT roll_no, name FROM studentDB.studentDetails where section=’A’ limit 5; \
+
+
+# Data Serialisation and storage
+
+1. In order to transport the data over the network or to store on some persistent storage, we use the process of translating data structures or objects state into binary or textual form. We call this process serialization..
+2. Avro data is stored in a container file (a .avro file) and its schema (the .avsc file) is stored with the data file.
+3. Apache Hive provides support to store a table as Avro and can also query data in this serialisation format.

courses/big_data/evolution.md

@@ -0,0 +1,3 @@
+# Evolution of Hadoop
+
+![Evolution of hadoop](images/hadoop_evolution.png)

courses/big_data/intro.md

@@ -0,0 +1,35 @@
+# School of SRE: Big Data
+
+## Pre - Reads
+
+- Basics of Linux File systems.
+- Basic understanding of System Design.
+
+## Target Audience
+
+The concept of Big Data has been around for years; most organizations now understand that if they capture all the data that streams into their businesses, they can apply analytics and get significant value from it. 
+This training material covers the basics of Big Data(using Hadoop) for beginners, who would like to quickly get started and get their hands dirty in this domain.
+
+## What to expect from this training 
+
+This course covers the basics of Big Data and how it has evolved to become what it is today. We will take a look at a few realistic scenarios where Big Data would be a perfect fit. An interesting assignment on designing a Big Data system is followed by understanding the architecture of Hadoop and the tooling around it. 
+
+## What is not covered under this training
+
+Writing programs to draw analytics from data.
+
+## TOC:
+
+1. Overview of Big Data
+2. Usage of Big Data techniques
+3. Evolution of Hadoop
+4. Architecture of hadoop
+    1. HDFS
+    2. Yarn
+5. MapReduce framework
+6. Other tooling around hadoop
+    1. Hive
+    2. Pig
+    3. Spark
+    4. Presto
+7. Data Serialisation and storage

courses/big_data/overview.md

@@ -0,0 +1,13 @@
+# Overview of Big Data
+
+1. Big Data is a collection of large datasets that cannot be processed using traditional computing techniques. It is not a single technique or a tool, rather it has become a complete subject, which involves various tools, techniques and frameworks.
+2. Big Data could consist of
+    1. Structured data
+    2. Unstructured data
+    3. Semi-structured data
+3. Characteristics of Big Data:
+    4. Volume
+    5. Variety
+    6. Velocity
+    7. Variability
+4. Examples of Big Data generation include stock exchanges, social media sites, jet engines, etc.

courses/big_data/tasks.md

@@ -0,0 +1,14 @@
+# Tasks and conclusion
+
+## Post training tasks:
+
+1. Try setting up your own 3 node hadoop cluster. 
+    1. A VM based solution can be found [here](http://hortonworks.com/wp-content/uploads/2015/04/Import_on_VBox_4_07_2015.pdf)
+2. Write a simple spark/MR job of your choice and understand how to generate analytics from data.
+    1. Sample dataset can be found [here](https://grouplens.org/datasets/movielens/)
+
+## References:
+1. [Hadoop documentation](http://hadoop.apache.org/docs/current/)
+2. [HDFS Architecture](http://hadoop.apache.org/docs/current/hadoop-project-dist/hadoop-hdfs/HdfsDesign.html)
+3. [YARN Architecture](http://hadoop.apache.org/docs/current/hadoop-yarn/hadoop-yarn-site/YARN.html)
+4. [Google GFS paper](https://storage.googleapis.com/pub-tools-public-publication-data/pdf/035fc972c796d33122033a0614bc94cff1527999.pdf)

courses/big_data/usage.md

@@ -0,0 +1,10 @@
+# Usage of Big Data techniques
+
+1. Take the example of the traffic lights problem.
+    1. There are more than 300,000 traffic lights in the US as of 2018.
+    2. Let us assume that we placed a device on each of them to collect metrics and send it to a central metrics collection system.
+    3. If each of the IOT devices sends 10 events per minute, we have 300000x10x60x24 = 432x10^7 events per day.
+    4. How would you go about processing that and telling me how many of the signals were “green” at 10:45 am on a particular day?
+2. Consider the next example on Unified Payments Interface (UPI) transactions:
+    1. We had about 1.15 billion UPI transactions in the month of October, 2019 in India.
+    12. If we try to extrapolate this data to about a year and try to find out some common payments that were happening through a particular UPI ID, how do you suggest we go about that?

mkdocs.yml

@@ -18,3 +18,10 @@ nav:
     - Availability: systems_design/availability.md
     - Fault Tolerance: systems_design/fault-tolerance.md
     - Conclusion: systems_design/conclusion.md
+- Big Data:
+    - Intro: big_data/intro.md
+    - Overview of Big Data: big_data/overview.md
+    - Usage of Big Data techniques: big_data/usage.md
+    - Evolution of Hadoop: big_data/evolution.md
+    - Architecture of Hadoop: big_data/architecture.md
+    - Tasks and conclusion: big_data/tasks.md