Merge pull request #1 from donnemartin/master

merge with master
pull/71/head
Madalin Ilie 2017-04-03 14:47:49 +03:00 committed by GitHub
commit d396ac79de
19 changed files with 24 additions and 10 deletions

View File

@ -7,11 +7,11 @@
## Motivation ## Motivation
> Learn how to design large scale systems. > Learn how to design large-scale systems.
> >
> Prep for the system design interview. > Prep for the system design interview.
### Learn how to design large scale systems ### Learn how to design large-scale systems
Learning how to design scalable systems will help you become a better engineer. Learning how to design scalable systems will help you become a better engineer.
@ -54,6 +54,19 @@ The provided [Anki flashcard decks](https://apps.ankiweb.net/) use spaced repeti
Great for use while on-the-go. Great for use while on-the-go.
### Coding Resource: Interactive Coding Challenges
Looking for resources to help you prep for the [**Coding Interview**](https://github.com/donnemartin/interactive-coding-challenges)?
<p align="center">
<img src="http://i.imgur.com/b4YtAEN.png">
<br/>
</p>
Check out the sister repo [**Interactive Coding Challenges**](https://github.com/donnemartin/interactive-coding-challenges), which contains an additional Anki deck:
* [Coding deck](anki_cards/https://github.com/donnemartin/interactive-coding-challenges/tree/master/anki_cards/Coding.apkg)
## Contributing ## Contributing
> Learn from the community. > Learn from the community.
@ -1330,12 +1343,13 @@ A basic HTTP request consists of a verb (method) and a resource (endpoint). Bel
*Can be called many times without different outcomes. *Can be called many times without different outcomes.
The difference between `PUT` and `PATCH` is explained by example [here](https://laracasts.com/discuss/channels/general-discussion/whats-the-differences-between-put-and-patch?page=1).
HTTP is an application layer protocol relying on lower-level protocols such as **TCP** and **UDP**. HTTP is an application layer protocol relying on lower-level protocols such as **TCP** and **UDP**.
* [HTTP](https://www.nginx.com/resources/glossary/http/) #### Source(s) and further reading: HTTP
* [README](https://www.quora.com/What-is-the-difference-between-HTTP-protocol-and-TCP-protocol)
* [What is HTTP?](https://www.nginx.com/resources/glossary/http/)
* [Difference between HTTP and TCP](https://www.quora.com/What-is-the-difference-between-HTTP-protocol-and-TCP-protocol)
* [Difference between PUT and PATCH](https://laracasts.com/discuss/channels/general-discussion/whats-the-differences-between-put-and-patch?page=1)
### Transmission control protocol (TCP) ### Transmission control protocol (TCP)
@ -1423,12 +1437,12 @@ POST /anotheroperation
RPC is focused on exposing behaviors. RPCs are often used for performance reasons with internal communications, as you can hand-craft native calls to better fit your use cases. RPC is focused on exposing behaviors. RPCs are often used for performance reasons with internal communications, as you can hand-craft native calls to better fit your use cases.
Choose a Native Library aka SDK when: Choose a native library (aka SDK) when:
* You know your target platform. * You know your target platform.
* You want to control how your "logic" is accessed * You want to control how your "logic" is accessed.
* You want to control how error control happens off your library * You want to control how error control happens off your library.
* Performance and end user experience is your primary concern * Performance and end user experience is your primary concern.
HTTP APIs following **REST** tend to be used more often for public APIs. HTTP APIs following **REST** tend to be used more often for public APIs.

Binary file not shown.

BIN
resources/study_guide.png Normal file

Binary file not shown.

After

Width:  |  Height:  |  Size: 167 KiB

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.

Binary file not shown.