From d40ba34d64e9ced0ab76dcf8fcccfa1473adade9 Mon Sep 17 00:00:00 2001 From: Donne Martin Date: Sun, 2 Apr 2017 08:00:20 -0400 Subject: [PATCH 1/3] Add sources and further reading to HTTP section --- README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index e7d8cd96..7dafd652 100644 --- a/README.md +++ b/README.md @@ -1330,12 +1330,13 @@ A basic HTTP request consists of a verb (method) and a resource (endpoint). Bel *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](https://www.nginx.com/resources/glossary/http/) -* [README](https://www.quora.com/What-is-the-difference-between-HTTP-protocol-and-TCP-protocol) +#### Source(s) and further reading: HTTP + +* [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) From 8fc20e606d643124187b9ff165aacb32b3e58cc6 Mon Sep 17 00:00:00 2001 From: Donne Martin Date: Sun, 2 Apr 2017 08:02:03 -0400 Subject: [PATCH 2/3] Fix caps and punctuation in RPC section --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 7dafd652..feddd97b 100644 --- a/README.md +++ b/README.md @@ -1424,12 +1424,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. -Choose a Native Library aka SDK when: +Choose a native library (aka SDK) when: * You know your target platform. -* You want to control how your "logic" is accessed -* You want to control how error control happens off your library -* Performance and end user experience is your primary concern +* You want to control how your "logic" is accessed. +* You want to control how error control happens off your library. +* Performance and end user experience is your primary concern. HTTP APIs following **REST** tend to be used more often for public APIs. From 591fa4f6a2f9e4651239e2f737f5db3eee3a62db Mon Sep 17 00:00:00 2001 From: Donne Martin Date: Sun, 2 Apr 2017 08:04:58 -0400 Subject: [PATCH 3/3] Change large scale -> large-scale --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index feddd97b..82e71962 100644 --- a/README.md +++ b/README.md @@ -7,11 +7,11 @@ ## Motivation -> Learn how to design large scale systems. +> Learn how to design large-scale systems. > > 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.