content

.gitignore

@@ -0,0 +1 @@
+.vscode

mitocw/l01.txt

@@ -0,0 +1,30 @@
+
+
+
+1. parallelism
+2. fault tolerance
+3. transactions across sites eg banks
+4. security, isolation, contain it.
+
+
+1. too many moving parts, concurrent programming
+2. unexpected failure patterns.
+3. partial failures
+4. actual vs ideal performance
+
+lab 1
+mapreduce
+
+
+lab 2
+raft
+
+
+lab 3
+
+k/v server
+
+
+lab 4 
+
+sharted key value service

systemdesig_template.rst

@@ -15,37 +15,29 @@ Features
 ========
 
 - The feature set 
-        
         Make note of the specs carefully. Feel free to annotate a bit
 
 - Define APIs and Endpoints. 
-
         Knowing what routes will be hit by the public and what sort of auth is being used is essential
 
 - Availability
-
         What to do if a host goes down, what to do if the entire data centre goes down. If already exists then enquire about the current plans and also ascertain the amount of availability cared about
 
 - Latency Performance
-
         Public facing services require snappy responses. This may be kept track of with monitoring tools.
 
 - Scalability
 
 - Durability
-
         At times data can be stored in a db securely without loss and compromises what sort of dbs am I working with.
 
 - Class Diagrams
-
         OOP diagrams basically, they may ask to design some parking lot or elevator systems
 
 - Security and Privacy
-
         TLDR: When users and auth are required these practices will become sacrosanct
 
 - Cost Effective
-
         Lean systems are not only cost effective but easier to maintain. KISS. Check Pros and Cons for current and alt flows
 
 
@@ -132,7 +124,6 @@ Types of NoSQL
         Note current conf
 
 ---
-
 Caching
 -------
 
@@ -146,7 +137,7 @@ Points of Concern:
 - cannot be accepted as source of truth
 
 Data Centers/Racks/Hosts
------------------------
+------------------------
 
 Key points of interest may be:
 
@@ -188,6 +179,7 @@ IPV4 vs IPV6
 
 - runnin out of ipv4 addys
 - ipv4 = 32 bits vs ipv6 = 128bits (remember go-discord-irc conundrum)
+- Some power systems 
 
 
 TCP vs UDP
@@ -220,8 +212,7 @@ PKI and CAs
 
 - We know that CAs verify that the certs or pubkeys are actually good to go ie they are recognized and authorized.
 - Prevents MITM
-- See ``Georg`` for more info.
-
+- See ``Georg`` for more if- eg avao;
 
 Symmetric vs Asymmetric Encryption
 ----------------------------------
@@ -249,3 +240,19 @@ Bloom Filters and Count-min sketch
 - Space efficient probablisitic based data structures.
 - BF - Used to decide to an element is a part of a set or not. May have false positives but never false negatives. Very Space Efficient (READ MORE)
 - CMS - Frequency event counter. fraction of space used to probablistically arrive at close to the accurate answer.
+
+Paxos
+-----
+
+
+VMS and Containers
+-------------------
+
+- vm is system on system, containers self contained
+
+Map Reduce
+------------
+
+
+Concurrency, threading
+-----------------------

systemtools.rst

@@ -0,0 +1,79 @@
+========
+Toolkit
+========
+
+list
+=========
+
+cassandra
+---------
+
+- wide column
+- time series Data
+- consistent hash Sharding
+- eventual consistency, gossipping
+
+mongodb
+-------
+
+- json??
+
+memcached
+---------
+
+- distrib cache key value storage
+
+Apache kafka
+------------
+
+zookeeper
+---------
+
+mysql
+-----
+- master slave architecture
+
+
+redis
+-----
+
+- memcache on steroids
+- can be clustered
+
+HAPROXY
+-------
+
+Nginx
+-----
+
+
+kafka
+-----
+
+solr
+----
+
+elasticsearch
+-------------
+
+
+blobstore
+----------
+
+
+docker
+------
+
+
+kube and mesos
+--------------
+
+spark (map reduce)
+-------------------
+
+hdfs
+----
+
+java based fs
+
+