--- title: Davide's Code and Architecture Notes - L4 vs L7 Load... description: A load balancer sits in front of applications to distribute incoming traffic, handle service discovery, abstraction, and health checking. The piece explains... canonical: https://daily.dev/posts/davide-s-code-and-architecture-notes---l4-vs-l7-load-balancer-2mozrvu4m twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Davide's Code and Architecture Notes - L4 vs L7 Load Balancer | daily.dev og:description: A load balancer sits in front of applications to distribute incoming traffic, handle service discovery, abstraction, and health checking. The piece explains... og:url: https://daily.dev/posts/davide-s-code-and-architecture-notes---l4-vs-l7-load-balancer-2mozrvu4m og:image: https://api.daily.dev/og/posts/2mozRVu4M.png og:image:alt: Davide's Code and Architecture Notes - L4 vs L7 Load Balancer og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Davide's Code and Architecture Notes - L4 vs L7 Load Balancer **[Code4IT](https://daily.dev/sources/code4it)** · 8 min read · 0 upvotes · 0 comments ## Summary A load balancer sits in front of applications to distribute incoming traffic, handle service discovery, abstraction, and health checking. The piece explains the OSI model's seven layers, then contrasts L7 (application layer) load balancers—which route based on full request content, enabling SSL termination, authentication, and observability—with L4 (transport layer) load balancers, which work only with TCP/UDP and IP addresses, making them faster but less feature-rich. A comparison table summarizes the differences, and links to Azure Application Gateway, AWS ELB, Traefik, and NGINX are given as examples of L7 tools. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is the difference between an L4 and an L7 load balancer? An L4 load balancer operates at the transport layer, routing traffic based on TCP/UDP protocols and IP addresses without inspecting request content, making it fast but limited to simple algorithms. An L7 load balancer works at the application layer, inspecting HTTP headers, URLs, and message content, enabling routing, SSL termination, authentication, and observability, at the cost of added complexity. _daily.dev surfaces system design explainers like this for engineers weighing load balancer choices._ ### What functionalities can an L7 load balancer provide beyond basic routing? An L7 load balancer can perform SSL termination to offload encryption/decryption from backend servers, authentication by checking HTTP headers and returning 401 responses, observability through tracing requests and response times, and security protections such as DDoS mitigation, in addition to content-aware routing like sending image requests to dedicated servers. _Developers designing resilient traffic layers can track these load balancing patterns on daily.dev._ ### What happens if one server becomes unhealthy behind a load balancer handling 100 requests per second? If two servers each handle 50 requests per second and one becomes unhealthy, the load balancer removes it and routes all 100 requests per second to the remaining server. If that server cannot absorb the spike, the entire application can go offline, which is why simply shifting all traffic to a single healthy instance should be avoided. _Teams planning for failover scenarios can follow load balancing and resilience content on daily.dev._ ## Similar posts on daily.dev - [What Is a Load Balancer?](https://daily.dev/posts/what-is-a-load-balancer--hpaid5n1e) · Isovalent · 3 upvotes · 0 comments - [What Every Engineer Should Know About TCP, Kernel Memory, and Load Balancers](https://daily.dev/posts/what-every-engineer-should-know-about-tcp-kernel-memory-and-load-balancers-3tu8a9dba) · gitconnected · 0 upvotes · 0 comments - [Basic Web Application Architecture — Design Explanation](https://daily.dev/posts/basic-web-application-architecture-design-explanation-z6gdpiaxz) · Medium · 0 upvotes · 0 comments - [EP208: Load Balancer vs API Gateway](https://daily.dev/posts/ep208-load-balancer-vs-api-gateway-oii0fuod4) · ByteByteGo · 22 upvotes · 1 comments - [Why application security must start at the load balancer](https://daily.dev/posts/why-application-security-must-start-at-the-load-balancer-bivznty2c) · CSO Online · 0 upvotes · 0 comments --- Tags: [#career](https://daily.dev/tags/career), [#networking](https://daily.dev/tags/networking), [#nginx](https://daily.dev/tags/nginx) [View this post on daily.dev](https://daily.dev/posts/davide-s-code-and-architecture-notes---l4-vs-l7-load-balancer-2mozrvu4m) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Davide's Code and Architecture Notes - L4 vs L7 Load Balancer","url":"https://daily.dev/posts/davide-s-code-and-architecture-notes---l4-vs-l7-load-balancer-2mozrvu4m","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/davide-s-code-and-architecture-notes---l4-vs-l7-load-balancer-2mozrvu4m"},"datePublished":"2026-10-04T13:06:39.873Z","dateModified":"2026-10-04T13:15:50.710Z","description":"A load balancer sits in front of applications to distribute incoming traffic, handle service discovery, abstraction, and health checking. The piece explains...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3fa93c96d63f2d06f820912e1719204c?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3fa93c96d63f2d06f820912e1719204c?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Code4IT","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Code4IT","logo":"https://media.daily.dev/image/upload/s--OaaG4G10--/f_auto,q_auto/v1791119049/logos/code4it?_a=BAMAMicg0","url":"https://daily.dev/sources/code4it"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/davide-s-code-and-architecture-notes---l4-vs-l7-load-balancer-2mozrvu4m","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"career,networking,nginx","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Code4IT","item":"https://daily.dev/sources/code4it"},{"@type":"ListItem","position":3,"name":"Davide's Code and Architecture Notes - L4 vs L7 Load Balancer"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/davide-s-code-and-architecture-notes---l4-vs-l7-load-balancer-2mozrvu4m#faq","mainEntity":[{"@type":"Question","name":"What is the difference between an L4 and an L7 load balancer?","acceptedAnswer":{"@type":"Answer","text":"An L4 load balancer operates at the transport layer, routing traffic based on TCP/UDP protocols and IP addresses without inspecting request content, making it fast but limited to simple algorithms. An L7 load balancer works at the application layer, inspecting HTTP headers, URLs, and message content, enabling routing, SSL termination, authentication, and observability, at the cost of added complexity. daily.dev surfaces system design explainers like this for engineers weighing load balancer choices."}},{"@type":"Question","name":"What functionalities can an L7 load balancer provide beyond basic routing?","acceptedAnswer":{"@type":"Answer","text":"An L7 load balancer can perform SSL termination to offload encryption/decryption from backend servers, authentication by checking HTTP headers and returning 401 responses, observability through tracing requests and response times, and security protections such as DDoS mitigation, in addition to content-aware routing like sending image requests to dedicated servers. Developers designing resilient traffic layers can track these load balancing patterns on daily.dev."}},{"@type":"Question","name":"What happens if one server becomes unhealthy behind a load balancer handling 100 requests per second?","acceptedAnswer":{"@type":"Answer","text":"If two servers each handle 50 requests per second and one becomes unhealthy, the load balancer removes it and routes all 100 requests per second to the remaining server. If that server cannot absorb the spike, the entire application can go offline, which is why simply shifting all traffic to a single healthy instance should be avoided. Teams planning for failover scenarios can follow load balancing and resilience content on daily.dev."}}]} ```