Fixing links and standardising titles

This commit is contained in:
Kalyanasundaram Somasundaram 2020-11-23 20:16:23 +05:30
parent bf2c85d6b0
commit da2599ebe5
19 changed files with 63 additions and 73 deletions

View File

@ -13,9 +13,7 @@ This course covers the basics of Big Data and how it has evolved to become what
Writing programs to draw analytics from data.
## Course Content
### Table of Contents
## Course Contents
1. [Overview of Big Data](https://linkedin.github.io/school-of-sre/big_data/intro/#overview-of-big-data)
2. [Usage of Big Data techniques](https://linkedin.github.io/school-of-sre/big_data/intro/#usage-of-big-data-techniques)
@ -57,4 +55,4 @@ Writing programs to draw analytics from data.
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?

View File

@ -2,24 +2,24 @@
NoSQL:
https://hostingdata.co.uk/nosql-database/
[https://hostingdata.co.uk/nosql-database/](https://hostingdata.co.uk/nosql-database/)
https://www.mongodb.com/nosql-explained
[https://www.mongodb.com/nosql-explained](https://www.mongodb.com/nosql-explained)
https://www.mongodb.com/nosql-explained/nosql-vs-sql
[https://www.mongodb.com/nosql-explained/nosql-vs-sql](https://www.mongodb.com/nosql-explained/nosql-vs-sql)
Cap Theorem
http://www.julianbrowne.com/article/brewers-cap-theorem
[http://www.julianbrowne.com/article/brewers-cap-theorem](http://www.julianbrowne.com/article/brewers-cap-theorem)
Scalability
http://www.slideshare.net/jboner/scalability-availability-stability-patterns
[http://www.slideshare.net/jboner/scalability-availability-stability-patterns](http://www.slideshare.net/jboner/scalability-availability-stability-patterns)
Eventual Consistency
https://www.allthingsdistributed.com/2008/12/eventually_consistent.html
[https://www.allthingsdistributed.com/2008/12/eventually_consistent.html](https://www.allthingsdistributed.com/2008/12/eventually_consistent.html)
https://www.toptal.com/big-data/consistent-hashing
[https://www.toptal.com/big-data/consistent-hashing](https://www.toptal.com/big-data/consistent-hashing)
https://web.stanford.edu/class/cs244/papers/chord_TON_2003.pdf
[https://web.stanford.edu/class/cs244/papers/chord_TON_2003.pdf](https://web.stanford.edu/class/cs244/papers/chord_TON_2003.pdf)

View File

@ -11,16 +11,16 @@ At the end of training, you will have an understanding of what a NoSQL database
We will not be deep diving into any specific NoSQL Database.
## Table of Contents
## Course Contents
* Introduction to NoSQL
* CAP Theorem
* Data versioning
* Partitioning
* Hashing
* Quorum
* [Introduction to NoSQL](https://linkedin.github.io/school-of-sre/databases_nosql/intro/#introduction)
* [CAP Theorem](https://linkedin.github.io/school-of-sre/databases_nosql/key_concepts/#cap-theorem)
* [Data versioning](https://linkedin.github.io/school-of-sre/databases_nosql/key_concepts/#versioning-of-data-in-distributed-systems)
* [Partitioning](https://linkedin.github.io/school-of-sre/databases_nosql/key_concepts/#partitioning)
* [Hashing](https://linkedin.github.io/school-of-sre/databases_nosql/key_concepts/#hashing)
* [Quorum](https://linkedin.github.io/school-of-sre/databases_nosql/key_concepts/#quorum)
## Introduction

View File

@ -1,4 +1,4 @@
## Key Concepts
# Key Concepts
Lets looks at some of the key concepts when we talk about NoSQL or distributed systems

10
courses/git/conclusion.md Normal file
View File

@ -0,0 +1,10 @@
## What next from here?
There are a lot of git commands and features which we have not explored here. But with the base built-up, be sure to explore concepts like
- Cherrypick
- Squash
- Amend
- Stash
- Reset

View File

@ -16,9 +16,7 @@ As an engineer in the field of computer science, having knowledge of version con
Advanced usage and specifics of internal implementation details of Git.
## Course Content
### Table of Contents
## Course Contents
1. [Git Basics](https://linkedin.github.io/school-of-sre/git/git-basics/#git-basics)
2. [Working with Branches](https://linkedin.github.io/school-of-sre/git/branches/)

View File

@ -40,13 +40,3 @@ this is from pre commit hook # <===== THE MESSAGE FROM HOOK EXECUTION
1 file changed, 1 insertion(+)
create mode 100644 sample.txt
```
## What next from here?
There are a lot of git commands and features which we have not explored here. But with the base built-up, be sure to explore concepts like
- Cherrypick
- Squash
- Amend
- Stash
- Reset

View File

@ -17,7 +17,7 @@ In this course we are focusing on building strong foundational skills. The cours
- [Python and Web](https://linkedin.github.io/school-of-sre/python_web/intro/)
- Data
- Relational databases (MySQL)
- NoSQL concepts
- [NoSQL concepts](https://linkedin.github.io/school-of-sre/databases_nosql/intro/)
- [Big Data](https://linkedin.github.io/school-of-sre/big_data/intro/)
- [Systems Design](https://linkedin.github.io/school-of-sre/systems_design/intro/)
- [Security](https://linkedin.github.io/school-of-sre/security/intro/)

View File

@ -27,7 +27,7 @@ In the second and third part, we will be taking examples to understand the conce
We are not covering advanced linux commands and bash scripting in this
course. We will also not be covering linux internals.
## Course Content
## Course Contents
The following topics has been covered in this course:

View File

@ -12,13 +12,11 @@ Throughout the course, we cover how an SRE can optimize the system to improve th
This course spends time on the fundamentals. We are not covering concepts like HTTP/2.0, QUIC, TCP congestion control protocols, Anycast, BGP, CDN, Tunnels and Multicast. We expect that this course will provide the relevant basics to understand such concepts
## Course Content
### Birds eye view of the course
## Birds eye view of the course
The course covers the question “What happens when you open linkedin.com in your browser?” The course follows the flow of TCP/IP stack.More specifically, the course covers topics of Application layer protocols DNS and HTTP, transport layer protocols UDP and TCP, networking layer protocol IP and Data Link Layer protocol
## Table of Contents
## Course Contents
1. [DNS](https://linkedin.github.io/school-of-sre/linux_networking/dns/)
2. [UDP](https://linkedin.github.io/school-of-sre/linux_networking/udp/)
3. [HTTP](https://linkedin.github.io/school-of-sre/linux_networking/http/)

View File

@ -17,13 +17,11 @@ And to introduce SRE flavour to the course, we will design, develop and deploy (
Extensive knowledge of python internals and advanced python.
## Course Content
### Lab Environment Setup
## Lab Environment Setup
Have latest version of python installed
### Table of Contents
## Course Contents
1. [The Python Language](https://linkedin.github.io/school-of-sre/python_web/intro/#the-python-language)
1. Some Python Concepts

View File

@ -25,7 +25,7 @@ Now let's think in terms of the given url shortening app. We need to monitor it.
3. We also want to keep an eye on the database so depending on the database solution chosen. Query times, volumes, disk usage etc.
4. Finally, there also needs to be some external monitoring which runs periodic tests from devices outside of your data centers. This emulates customers and ensures that from customer point of view, the system is working as expected.
## SRE Use-cases
## Applications in SRE role
In the world of SRE, python is a widely used language. For small scripts and tooling developed for various purposes. Since tooling developed by SRE works with critical pieces of infrastructure and has great power (to bring things down), it is important to know what you are doing while using a programming language and its features. Also it is equally important to know the language and its characteristics while debugging the issues. As an SRE having a deeper understanding of python language, it has helped me a lot to debug very sneaky bugs and be generally more aware and informed while making certain design decisions.

View File

@ -14,3 +14,12 @@ Some books that would be a great resource
- How to Investigate Like a Rockstar <https://books2read.com/u/4jDWoZ>- Live a real crisis to master the secrets of forensic analysis, Sparc Flow, 2017
- Real World Cryptography <https://www.manning.com/books/real-world-cryptography>- This early-access book teaches you applied cryptographic techniques to understand and apply security at every level of your systems and applications.
- AWS Security <https://www.manning.com/books/aws-security?utm_source=github&utm_medium=organic&utm_campaign=book_shields_aws_1_31_20>- This early-access book covers commong AWS security issues and best practices for access policies, data protection, auditing, continuous monitoring, and incident response.
## Post Training asks/ Further Reading
- CTF Events like : <https://github.com/apsdehal/awesome-ctf>
- Penetration Testing : <https://github.com/enaqx/awesome-pentest>
- Threat Intelligence : <https://github.com/hslatman/awesome-threat-intelligence>
- Threat Detection & Hunting : <https://github.com/0x4D31/awesome-threat-detection>
- Web Security: <https://github.com/qazbnm456/awesome-web-security>
- Building Secure and Reliable Systems : <https://landing.google.com/sre/resources/foundationsandprinciples/srs-book/>

View File

@ -2,9 +2,9 @@
## Prerequisites
1. Basics of Linux fundamentals & command line usage
1. [Linux Basics](https://linkedin.github.io/school-of-sre/linux_basics/intro/)
2. Networking Module
2. [Linux Networking](https://linkedin.github.io/school-of-sre/linux_networking/intro/)
## What to expect from this course
@ -17,22 +17,10 @@ The course covers fundamentals of information security along with touching on su
The courseware is not an ethical hacking workshop or a very deep dive into the fundamentals of the problems. The course does not deal with hacking or breaking into systems but rather an approach on how to ensure you dont get into those situations and also to make you aware of different ways a system can be compromised.
## Course Content
### Table of Contents
## Course Contents
1. [Fundamentals](https://linkedin.github.io/school-of-sre/security/fundamentals/)
2. [Network Security](https://linkedin.github.io/school-of-sre/security/network_security/)
3. [Threats, Attacks & Defence](https://linkedin.github.io/school-of-sre/security/threats_attacks_defences/)
4. [Writing Secure Code & More](https://linkedin.github.io/school-of-sre/security/writing_secure_code/)
5. [Conclusion](https://linkedin.github.io/school-of-sre/security/conclusion/)
## Post Training asks/ Further Reading
- CTF Events like : <https://github.com/apsdehal/awesome-ctf>
- Penetration Testing : <https://github.com/enaqx/awesome-pentest>
- Threat Intelligence : <https://github.com/hslatman/awesome-threat-intelligence>
- Threat Detection & Hunting : <https://github.com/0x4D31/awesome-threat-detection>
- Web Security: <https://github.com/qazbnm456/awesome-web-security>
- Building Secure and Reliable Systems : <https://landing.google.com/sre/resources/foundationsandprinciples/srs-book/>

View File

@ -76,7 +76,7 @@ The combined availability of the system is
**KEY TAKEAWAYS:** Strive for active/active rather than active/passive solutions, they have a lesser risk of cross over being unreliable. Use LB and right load balancing methods to ensure reliable failover. Model and build your data systems to ensure data is correctly handled when crossover happens. Generally DB systems follow active/passive semantics for writes. Masters accept writes and when master goes down, follower is promoted to master(active from being passive) to accept writes. We have to be careful here that the cutover never introduces more than one masters. This problem is called a split brain.
## SRE Use cases
## Applications in SRE role
1. SRE works on deciding an acceptable SLA and make sure system is available to achieve the SLA
2. SRE is involved in architecture design right from building the data center to make sure site is not affected by network switch, hardware, power or software failures
3. SRE also run mock drills of failures to see how the system behaves in uncharted territory and comes up with a plan to improve availability if there are misses.

View File

@ -60,7 +60,7 @@ Let's take another example, we come up with a new model for our Content sharing
- https://learning.oreilly.com/library/view/the-art-of/9780134031408/ch21.html#ch21
### SRE Use cases:
### Applications in SRE role
1. Work with the DC tech or cloud team to distribute infrastructure such that its immune to switch or power failures by creating fault zones within a Data Center
https://docs.microsoft.com/en-us/azure/virtual-machines/manage-availability#use-availability-zones-to-protect-from-datacenter-level-failures
2. Work with the partners and design interaction between services such that one service breakdown is not amplified in a cascading fashion to all upstreams

View File

@ -3,9 +3,11 @@
## Prerequisites
Fundamentals of common software system components:
- Operating Systems
- Networking
- Databases RDBMS/NoSQL
- [Linux Basics](https://linkedin.github.io/school-of-sre/linux_basics/intro/)
- [Linux Networking](https://linkedin.github.io/school-of-sre/linux_networking/intro/)
- Databases RDBMS
- [NoSQL Concepts](https://linkedin.github.io/school-of-sre/databases_nosql/intro/)
## What to expect from this course
@ -17,9 +19,7 @@ Individual software components scalability and reliability concerns like e.g.
More light will be shed on concepts rather than on setting up and configuring components like Loadbalancers to achieve scalability, availability and reliability of systems
## Course Content
### Table of Contents
## Course Contents
- [Introduction](https://linkedin.github.io/school-of-sre/systems_design/intro/#backstory)
- [Scalability](https://linkedin.github.io/school-of-sre/systems_design/scalability/)

View File

@ -171,7 +171,7 @@ Here the whole data centre is split and replicated and clients are directed to a
## SRE Use cases
## Applications in SRE role
1. SREs in coordination with the network team work on how to map users traffic to a particular site.
https://engineering.linkedin.com/blog/2017/05/trafficshift--load-testing-at-scale
2. SREs work closely with the Dev team to split monoliths to multiple microservices that are easy to run and manage

View File

@ -18,6 +18,7 @@ nav:
- Git Basics: git/git-basics.md
- Working With Branches: git/branches.md
- Github and Hooks: git/github-hooks.md
- Conclusion: git/conclusion.md
- Linux Networking:
- Introduction: linux_networking/intro.md
- DNS: linux_networking/dns.md
@ -33,14 +34,14 @@ nav:
- The URL Shortening App: python_web/url-shorten-app.md
- Conclusion: python_web/sre-conclusion.md
- Data:
- Big Data:
- Introduction: big_data/intro.md
- Evolution and Architecure of Hadoop: big_data/evolution.md
- Tasks and conclusion: big_data/tasks.md
- NoSQL Concepts:
- Introduction: databases_nosql/intro.md
- Key Concepts: databases_nosql/key_concepts.md
- References: databases_nosql/further_reading.md
- Conclusion: databases_nosql/further_reading.md
- Big Data:
- Introduction: big_data/intro.md
- Evolution and Architecure of Hadoop: big_data/evolution.md
- Conclusion: big_data/tasks.md
- Systems Design:
- Introduction: systems_design/intro.md
- Scalability: systems_design/scalability.md