--- title: The closer to the edge, the more stable a platform must be description: Different layers of a platform carry different reliability responsibilities. Deep services (databases, business logic) focus on correctness, middle-layer... canonical: https://daily.dev/posts/the-closer-to-the-edge-the-more-stable-a-platform-must-be-1rptuv5sk twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: The closer to the edge, the more stable a platform must be | daily.dev og:description: Different layers of a platform carry different reliability responsibilities. Deep services (databases, business logic) focus on correctness, middle-layer... og:url: https://daily.dev/posts/the-closer-to-the-edge-the-more-stable-a-platform-must-be-1rptuv5sk og:image: https://api.daily.dev/og/posts/1RpTuv5sk.png og:image:alt: The closer to the edge, the more stable a platform must be 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. # The closer to the edge, the more stable a platform must be **[ITNEXT](https://daily.dev/sources/itnext)** · 2 min read · 1 upvotes · 0 comments ## Summary Different layers of a platform carry different reliability responsibilities. Deep services (databases, business logic) focus on correctness, middle-layer orchestrators absorb failures through retries and compensating actions, and edge components like load balancers and API gateways prioritize availability above all else, shielding downstream systems from failure. The core argument is that the closer a component sits to the customer, the more it must prioritize stability over other concerns. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### why should api gateways and load balancers prioritize availability over business logic Edge components like load balancers and API gateways sit closest to the customer, so their primary job is absorbing failures from everything behind them rather than enforcing business correctness. They stay stateless, dependency-light, and fast, using timeouts, retries, load shedding, and traffic failover to protect backend systems, while deeper services focus on correctness like transaction rollbacks and compensating actions. _daily.dev surfaces architecture patterns like this for engineers designing resilient edge layers._ ## Similar posts on daily.dev - [To make a service more stable, eliminate dependencies](https://daily.dev/posts/to-make-a-service-more-stable-eliminate-dependencies-syibv7oj8) · ITNEXT · 0 upvotes · 0 comments - [Why Today’s Most Reliable Platforms Are Built to Expect Failure](https://daily.dev/posts/why-today-s-most-reliable-platforms-are-built-to-expect-failure-dbmcoaany) · SD Times · 0 upvotes · 0 comments - [Edge clouds and local data centers reshape IT](https://daily.dev/posts/edge-clouds-and-local-data-centers-reshape-it-wajhjtn2g) · InfoWorld · 0 upvotes · 0 comments - [Reliability is a Product Decision](https://daily.dev/posts/reliability-is-a-product-decision-wpmua7ypy) · Erlang Solutions · 1 upvotes · 0 comments --- Tags: [#career](https://daily.dev/tags/career), [#microservices](https://daily.dev/tags/microservices), [#api-gateway](https://daily.dev/tags/api-gateway) [View this post on daily.dev](https://daily.dev/posts/the-closer-to-the-edge-the-more-stable-a-platform-must-be-1rptuv5sk) ```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":"The closer to the edge, the more stable a platform must be","url":"https://daily.dev/posts/the-closer-to-the-edge-the-more-stable-a-platform-must-be-1rptuv5sk","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/the-closer-to-the-edge-the-more-stable-a-platform-must-be-1rptuv5sk"},"datePublished":"2026-08-18T07:31:17.959Z","dateModified":"2026-09-13T20:58:50.037Z","description":"Different layers of a platform carry different reliability responsibilities. Deep services (databases, business logic) focus on correctness, middle-layer...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ab5212694577d60fffc5b393011ba066?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ab5212694577d60fffc5b393011ba066?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ITNEXT","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":"ITNEXT","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/itnext2","url":"https://daily.dev/sources/itnext"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/the-closer-to-the-edge-the-more-stable-a-platform-must-be-1rptuv5sk","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"career,microservices,api-gateway","timeRequired":"PT2M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ITNEXT","item":"https://daily.dev/sources/itnext"},{"@type":"ListItem","position":3,"name":"The closer to the edge, the more stable a platform must be"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/the-closer-to-the-edge-the-more-stable-a-platform-must-be-1rptuv5sk#faq","mainEntity":[{"@type":"Question","name":"why should api gateways and load balancers prioritize availability over business logic","acceptedAnswer":{"@type":"Answer","text":"Edge components like load balancers and API gateways sit closest to the customer, so their primary job is absorbing failures from everything behind them rather than enforcing business correctness. They stay stateless, dependency-light, and fast, using timeouts, retries, load shedding, and traffic failover to protect backend systems, while deeper services focus on correctness like transaction rollbacks and compensating actions. daily.dev surfaces architecture patterns like this for engineers designing resilient edge layers."}}]} ```