Skip to content
GitLab
    • Explore Projects Groups Snippets
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • S system-design-primer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 173
    • Issues 173
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 190
    • Merge requests 190
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Donne Martin
  • system-design-primer
  • Merge requests
  • !52

Grammar issues in README.md

  • Review changes

  • Download
  • Email patches
  • Plain diff
Open Administrator requested to merge github/fork/CL123123/master into master 8 years ago
  • Overview 2
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: CL123123

"terminates" --> "terminate" "a new API results" --> "new API results"

Compare
  • version 1
    cbf9c7c1
    2 years ago

  • master (base)

and
  • latest version
    cbf9c7c1
    1 commit, 2 years ago

  • version 1
    cbf9c7c1
    1 commit, 2 years ago

1 file
+ 2
- 2

    Preferences

    File browser
    Compare changes
README.md
+ 2
- 2
  • View file @ cbf9c7c1

  • Edit in single-file editor

  • Open in Web IDE


Conflict: This file was modified in both the source and target branches. Ask someone with write access to resolve it.
@@ -646,7 +646,7 @@ Layer 4 load balancers look at info at the [transport layer](#communication) to
### layer 7 load balancing
Layer 7 load balancers look at the [application layer](#communication) to decide how to distribute requests. This can involve contents of the header, message, and cookies. Layer 7 load balancers terminates network traffic, reads the message, makes a load-balancing decision, then opens a connection to the selected server. For example, a layer 7 load balancer can direct video traffic to servers that host videos while directing more sensitive user billing traffic to security-hardened servers.
Layer 7 load balancers look at the [application layer](#communication) to decide how to distribute requests. This can involve contents of the header, message, and cookies. Layer 7 load balancers terminate network traffic, reads the message, makes a load-balancing decision, then opens a connection to the selected server. For example, a layer 7 load balancer can direct video traffic to servers that host videos while directing more sensitive user billing traffic to security-hardened servers.
    • Administrator
      Administrator @root · 8 years ago
      Author Contributor

      Created by: donnemartin

      Nice catch!

      • Please register or sign in to reply
Please register or sign in to reply
At the cost of flexibility, layer 4 load balancing requires less time and computing resources than Layer 7, although the performance impact can be minimal on modern commodity hardware.
@@ -728,7 +728,7 @@ Additional benefits include:
<i><a href=http://lethain.com/introduction-to-architecting-systems-for-scale/#platform_layer>Source: Intro to architecting systems for scale</a></i>
</p>
Separating out the web layer from the application layer (also known as platform layer) allows you to scale and configure both layers independently. Adding a new API results in adding application servers without necessarily adding additional web servers.
Separating out the web layer from the application layer (also known as platform layer) allows you to scale and configure both layers independently. Adding new API results in adding application servers without necessarily adding additional web servers.
    • Administrator
      Administrator @root · 8 years ago
      Author Contributor

      Created by: donnemartin

      Adding new API

      I think this should be Adding new APIs?

      • Please register or sign in to reply
Please register or sign in to reply
The **single responsibility principle** advocates for small and autonomous services that work together. Small teams with small services can plan more aggressively for rapid growth.
0 Assignees
None
Assign to
0 Reviewers
None
Request review from
Labels
3
closing-soon-if-no-response incorporating-feedback response-needed
3
closing-soon-if-no-response incorporating-feedback response-needed
    Assign labels
  • Manage project labels

Milestone
No milestone
None
None
Time tracking
No estimate or time spent
Lock merge request
Unlocked
1
1 participant
Administrator
Reference: donnemartin/system-design-primer!52
Source branch: github/fork/CL123123/master

Menu

Explore Projects Groups Snippets