sumitkumar1882 / cloud-university

Cloud University

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Cloud University

I created this as a study plan of topics for becoming an engineer in the Cloud Age.

Happy Codingd

What Is Cloud Computing?

Cloud computing is the on-demand delivery of IT resources and applications via the Internet with pay-as-you-go pricing. Whether you run applications that share photos to millions of mobile users or deliver services that support the critical operations of your business, the cloud provides rapid access to flexible and low-cost IT resources. With cloud computing, you don’t need to make large up-front investments in hardware and spend a lot of time managing that hardware. Instead, you can provision exactly the right type and size of computing resources you need to power your newest bright idea or operate your IT department. With cloud computing, you can access as many resources as you need, almost instantly, and only pay for what you use.

In its simplest form, cloud computing provides an easy way to access servers, storage, databases, and a broad set of application services over the Internet. Cloud computing providers such as AWS own and maintain the network-connected hardware required for these application services, while you provision and use what you need for your workloads.

What is Cloud University?

This is a study plan for going from a new grad to an engineer working on Cloud.

This is meant for software engineers or those switching from software/web development to a Cloud Engineer (where a wide range of computer science knowledge is required). If you have many years of experience and are claiming many years of software engineering experience, expect a harder requirement.

If you have many years of software/web development experience, note that large software companies like Google, Amazon, Facebook and Microsoft view software engineering as different from software/web development, and they require computer science knowledge.

If you want to be a Cloud Engineer, study more from the optional list (networking, security).

Copyright

Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.


Table of Contents


Don't feel you aren't smart enough

Interview Process & General Interview Prep

DevOps | SRE Roadmap

DevOps Roadmap

Pick One Language

You can use a language you are comfortable in to do the coding part of the interview, but for large companies, these are solid choices:

  • C++
  • Java
  • Python

You could also use these, but read around first. There may be caveats:

  • JavaScript
  • Ruby

You need to be very comfortable in the language and be knowledgeable.

Read more about choices:

See language resources here

You'll see some C, C++, and Python learning included below, because I'm learning. There are a few books involved, see the bottom.

Book List

This is a shorter list than what I used. This is abbreviated to save you time.

Interview Prep

If you have tons of extra time:

Computer Architecture

If short on time:

  • Write Great Code: Volume 1: Understanding the Machine
    • The book was published in 2004, and is somewhat outdated, but it's a terrific resource for understanding a computer in brief.
    • The author invented HLA, so take mentions and examples in HLA with a grain of salt. Not widely used, but decent examples of what assembly looks like.
    • These chapters are worth the read to give you a nice foundation:
      • Chapter 2 - Numeric Representation
      • Chapter 3 - Binary Arithmetic and Bit Operations
      • Chapter 4 - Floating-Point Representation
      • Chapter 5 - Character Representation
      • Chapter 6 - Memory Organization and Access
      • Chapter 7 - Composite Data Types and Memory Objects
      • Chapter 9 - CPU Architecture
      • Chapter 10 - Instruction Set Architecture
      • Chapter 11 - Memory Architecture and Organization

If you have more time (I want this book):

Language Specific

You need to choose a language for the interview (see above). Here are my recommendations by language. I don't have resources for all languages. I welcome additions.

If you read though one of these, you should have all the data structures and algorithms knowledge you'll need to start doing coding problems. You can skip all the video lectures in this project, unless you'd like a review.

Additional language-specific resources here.

C++

I haven't read these two, but they are highly rated and written by Sedgewick. He's awesome.

If you have a better recommendation for C++, please let me know. Looking for a comprehensive resource.

Python

Optional Books

Some people recommend these, but I think it's going overboard, unless you have many years of software engineering experience and expect a much harder interview:

  • Algorithm Design Manual (Skiena)

    • As a review and problem recognition
    • The algorithm catalog portion is well beyond the scope of difficulty you'll get in an interview.
    • This book has 2 parts:
      • class textbook on data structures and algorithms
        • pros:
          • is a good review as any algorithms textbook would be
          • nice stories from his experiences solving problems in industry and academia
          • code examples in C
        • cons:
          • can be as dense or impenetrable as CLRS, and in some cases, CLRS may be a better alternative for some subjects
          • chapters 7, 8, 9 can be painful to try to follow, as some items are not explained well or require more brain than I have
          • don't get me wrong: I like Skiena, his teaching style, and mannerisms, but I may not be Stony Brook material.
      • algorithm catalog:
        • this is the real reason you buy this book.
        • about to get to this part. Will update here once I've made my way through it.
    • Can rent it on kindle
    • Answers:
    • Errata
  • Introduction to Algorithms

    • Important: Reading this book will only have limited value. This book is a great review of algorithms and data structures, but won't teach you how to write good code. You have to be able to code a decent solution efficiently.
    • aka CLR, sometimes CLRS, because Stein was late to the game
  • Programming Pearls

    • The first couple of chapters present clever solutions to programming problems (some very old using data tape) but that is just an intro. This a guidebook on program design and architecture, much like Code Complete, but much shorter.
  • "Algorithms and Programming: Problems and Solutions" by Shen

    • A fine book, but after working through problems on several pages I got frustrated with the Pascal, do while loops, 1-indexed arrays, and unclear post-condition satisfaction results.
    • Would rather spend time on coding problems from another book or online coding problems.

Before you Get Started

This list grew over many months, and yes, it kind of got out of hand.

Here are some mistakes I made so you'll have a better experience.

1. You Won't Remember it All

I watched hours of videos and took copious notes, and months later there was much I didn't remember. I spent 3 days going through my notes and making flashcards so I could review.

Read please so you won't make my mistakes:

Retaining Computer Science Knowledge

2. Use Flashcards

To solve the problem, I made a little flashcards site where I could add flashcards of 2 types: general and code. Each card has different formatting.

I made a mobile-first website so I could review on my phone and tablet, wherever I am.

Make your own for free:

Keep in mind I went overboard and have cards covering everything from assembly language and Python trivia to machine learning and statistics. It's way too much for what's required.

Note on flashcards: The first time you recognize you know the answer, don't mark it as known. You have to see the same card and answer it several times correctly before you really know it. Repetition will put that knowledge deeper in your brain.

An alternative to using my flashcard site is Anki, which has been recommended to me numerous times. It uses a repetition system to help you remember. It's user-friendly, available on all platforms and has a cloud sync system. It costs $25 on iOS but is free on other platforms.

My flashcard database in Anki format: https://ankiweb.net/shared/info/25173560 (thanks @xiewenya)

3. Review, review, review

I keep a set of cheat sheets on ASCII, OSI stack, Big-O notations, and more. I study them when I have some spare time.

Take a break from programming problems for a half hour and go through your flashcards.

4. Focus

There are a lot of distractions that can take up valuable time. Focus and concentration are hard.

What you won't see covered

These are prevalent technologies but not part of this study plan:

  • SQL
  • Javascript
  • HTML, CSS, and other front-end technologies

The Daily Plan

Some subjects take one day, and some will take multiple days. Some are just learning with nothing to implement.

Each day I take one subject from the list below, watch videos about that subject, and write an implementation in:

  • C - using structs and functions that take a struct * and something else as args.
  • C++ - without using built-in types
  • C++ - using built-in types, like STL's std::list for a linked list
  • Python - using built-in types (to keep practicing Python)
  • and write tests to ensure I'm doing it right, sometimes just using simple assert() statements
  • You may do Java or something else, this is just my thing.

You don't need all these. You need only one language for the interview.

Why code in all of these?

  • Practice, practice, practice, until I'm sick of it, and can do it with no problem (some have many edge cases and bookkeeping details to remember)
  • Work within the raw constraints (allocating/freeing memory without help of garbage collection (except Python))
  • Make use of built-in types so I have experience using the built-in tools for real-world use (not going to write my own linked list implementation in production)

I may not have time to do all of these for every subject, but I'll try.

You can see my code here:

You don't need to memorize the guts of every algorithm.

Write code on a whiteboard or paper, not a computer. Test with some sample inputs. Then test it out on a computer.

Prerequisite Knowledge

Coding/OO

  • Be prepared to write around 20-30 lines of code in your strongest language.
  • You will be expected to design APIs, and use appropriate Object-Oriented Design and Programming.
  • Be sure to think about how to test your code, as well as come up with corner cases and edge cases.
  • Note that we focus on conceptual understanding, not memorization.
  • Our most successful candidates have spent time writing actual code using interview preparation websites like HackerRank, leet code, firecode.io or "​ ​mycodeschool​"​.
  • Sample Question: Given a single page of a book, find the longest word on that page.

Algorithms

Data Structures

You should study up on as many data structures as possible. Data structures most frequently used are arrays, linked lists, stacks, queues, hashsets, hashmaps, hash tables, dictionaries, trees and binary trees. You should know the data structure inside out, and what algorithms tend to go along with each data structure.

More Knowledge

Trees

Sorting

As a summary, here is a visual representation of 15 sorting algorithms. If you need more detail on this subject, see "Sorting" section in Additional Detail on Some Subjects

Graphs

Graphs can be used to represent many problems in computer science, so this section is long, like trees and sorting were.

You'll get more graph practice in Skiena's book (see Books section below) and the interview books

Even More Knowledge

System Design, Scalability, Data Handling

Tiny URL

Design a URL shortening service, like bit.ly

Step 1: Constraints and use cases

Use Cases

  1. Shortening: take a URL => return a much shorter URL
  2. Redirection: take a short URL => redirect to the original URL
  3. Custom URL
  4. High avaiability of the system

Constraints

Math:

  1. New URLs per month: 100 Million
  2. 1 Billion requests per month
  3. 10% from shortening and 90% from redirection
  4. Requests Per Second: 400+ (40: shortens, 360: redirects)
  5. Total URLs: 6 Billion URLs in 5 years
  6. 500 Bytes per URL
  7. 6 bytes per hash
  8. 3TBs for all URLs, 36GB for all hashes (over 5 years)
  9. New data written per second: 40 * (500 + 6): 20 KB
  10. Data read per second: 360 * 506 bytes: 180 KB

Step 2: Abstract design

  1. Application service layer (serves the requests)
  • Shortening service
  • Redirection service
  1. Data storage layer (keeps track of the hash => URL mappings)
  • Acts like a big hash table: stores new mappings, and retrieves a value given a key.
hashed_url = convert_to_base62(md5(original_url + random_salt))[:6]

Step 3: Understanding bottlenecks

Traffic is probably not goint ot be very hard, data - more interesting.

Step 4: Scaling your abstract design

  1. Application Service Layer
  • Start with one machine
  • Measure how far it takes us (load tests)
  • Add a load balancer + a cluster of machines over time: to deal with spike-y traffic, to increase availability
  1. Data Storage
  1. Billions of objects
  2. Each object is fairly small (< 1 KB)
  3. There are no relationships between the objects
  4. Reads are 9x more frequent than writes (360 reads, 40 writes per second)
  5. 3 TB of URLs, 36 GB of hashes

MySQL:

  • Widely used
  • Mature technology
  • Clear scaling paradigms (sharding, master/slave replication, master/master replication)
  • Used by Facebook, Twitter, Google, etc.
  • Index lookups are very fast

Tables:

mappings
    hash:varchar(6)
    original_url: varchar(512)
  1. Data Storage
  • Use one MySQL table with two varchar fields.
  • Create a unique index on the hash (36GB+). We want to hold it in memory to speed up lookups.
  • Vertical scaling of the MySQL machine for a while
  • Eventually, partition the data by taking the first char of the hash mod the number of partitions. Think about a master-slave setup(reading from the slaves, writes to the master).

Read more


Final Review

This section will have shorter videos that you can watch pretty quickly to review most of the important concepts.
It's nice if you want a refresher often.

Coding Question Practice

Now that you know all the computer science topics above, it's time to practice answering coding problems.

Coding question practice is not about memorizing answers to programming problems.

Why you need to practice doing programming problems:

  • problem recognition, and where the right data structures and algorithms fit in
  • gathering requirements for the problem
  • talking your way through the problem like you will in the interview
  • coding on a whiteboard or paper, not a computer
  • coming up with time and space complexity for your solutions
  • testing your solutions

There is a great intro for methodical, communicative problem solving in an interview. You'll get this from the programming interview books, too, but I found this outstanding: Algorithm design canvas

No whiteboard at home? That makes sense. I'm a weirdo and have a big whiteboard. Instead of a whiteboard, pick up a large drawing pad from an art store. You can sit on the couch and practice. This is my "sofa whiteboard". I added the pen in the photo for scale. If you use a pen, you'll wish you could erase. Gets messy quick.

my sofa whiteboard

Supplemental:

Read and Do Programming Problems (in this order):

See Book List above

Coding exercises/challenges

Once you've learned your brains out, put those brains to work. Take coding challenges every day, as many as you can.

Coding Interview Question Videos:

Challenge sites:

Challenge repos:

Mock Interviews:

[Troubleshooting]

Link

Monitoring and Logging

Operating Systems

Unix/Linux Internals

Web Technologies

Link

  • Know your network protocols and how the browser works, the HTTP protocol, cookies, general web troubleshooting (ability to diagnose issues step-by-step), Javascript and HTML.
  • Brush up on HTTP Protocol basics: PartI​,​ PartII

Networking

  • if you have networking experience or want to be a reliability engineer or operations engineer, expect questions
  • otherwise, this is just good to know
  • Link

Database

Link

Once you're closer to the interview

Your Resume

  • See Resume prep items in Cracking The Coding Interview and back of Programming Interviews Exposed

Be thinking of for when the interview comes

Think of about 20 interview questions you'll get, along with the lines of the items below. Have 2-3 answers for each. Have a story, not just data, about something you accomplished.

  • Why do you want this job?
  • What's a tough problem you've solved?
  • Biggest challenges faced?
  • Best/worst designs seen?
  • Ideas for improving an existing product.
  • How do you work best, as an individual and as part of a team?
  • Which of your skills or experiences would be assets in the role and why?
  • What did you most enjoy at [job x / project y]?
  • What was the biggest challenge you faced at [job x / project y]?
  • What was the hardest bug you faced at [job x / project y]?
  • What did you learn at [job x / project y]?
  • What would you have done better at [job x / project y]?

Have questions for the interviewer

Some of mine (I already may know answer to but want their opinion or team perspective):

  • How large is your team?
  • What does your dev cycle look like? Do you do waterfall/sprints/agile?
  • Are rushes to deadlines common? Or is there flexibility?
  • How are decisions made in your team?
  • How many meetings do you have per week?
  • Do you feel your work environment helps you concentrate?
  • What are you working on?
  • What do you like about it?
  • What is the work life like?

Once You've Got The Job

Congratulations!

Keep learning.

You're never really done.


*****************************************************************************************************
*****************************************************************************************************

Everything below this point is optional.
By studying these, you'll get greater exposure to more CS concepts, and will be better prepared for
any software engineering job. You'll be a much more well-rounded software engineer.

*****************************************************************************************************
*****************************************************************************************************

Additional Books

Additional Learning

These topics will likely not come up in an interview, but I added them to help you become a well-rounded software engineer, and to be aware of certain technologies and algorithms, so you'll have a bigger toolbox.

--

Additional Detail on Some Subjects

I added these to reinforce some ideas already presented above, but didn't want to include them
above because it's just too much. It's easy to overdo it on a subject.
You want to get hired in this century, right?

Video Series

Sit back and enjoy. "Netflix and skill" :P

Computer Science Courses

Introduction

Community

Version Control

Setup Arcanist
# Choose an installation directory (the directory instructions are optional, you can configure it where you want to save the configuration on your local)
$ cd $HOME
 
# git clone necessary repos
$ git clone https://github.com/phacility/libphutil.git
$ git clone https://github.com/phacility/arcanist.git
 
# Update your ~/.bash_profile file to update PATH environment variable to include arcanist bin directory
export PATH="$PATH:<arcanist_installation_directory>/arcanist/bin/"

CI/CD

Continuous Integration (CI)

  • Code
    • Cloud Source Repositories
    • GitHub
    • BitBucket
  • Build
    • Container Builder
    • Jenkins
    • CircleCI
  • Deploy
    • Deployment Manager
    • Spinnaker
    • Chef
    • Puppet
    • Ansible
    • Terraform
  • Test

Continuous Delivery (CD)

  • Code
  • Build
  • Deploy
  • Test
  • Release
    • Canary
    • Blue/green
  • Monitor
    • Stackdriver

Automation

Distributed Systems

Production Web App

Continuous Integration | Continuous Delivery

Containers

Web Servers

Nginx

Post-Mortem

Tools

  • OhMyZSH

Free at https://github.com/robbyrussell/oh-my-zsh

  • LastPass / 1Password /PassPack

The average person wastes hours each year resetting passwords they’ve forgotten. Password tools like these save time and mental energy by storing and autofilling your passwords. They also allow you to have long, unique passwords for each site, making it almost impossible for hackers to crack your password. Free at https://lastpass.com/ or https://agilebits.com/onepassword or https://www.passpack.com/

  • Flux

If you’ve ever had trouble sleeping after a long night of staring at your computer screen, Flux is for you! Your circadian rhythm can’t tell the difference between sunlight and the glow of a monitor. This free tool gradually changes your computer’s colors during and after sunset. Free at https://justgetflux.com/

Blogs

Questions to ask

Reference

About

Cloud University

License:MIT License