--- title: 5 Mistakes Teams Make When Scaling .NET Applications description: Scaling .NET applications is often hindered by infrastructure design mistakes rather than application code issues. Five common pitfalls are covered: ignoring... canonical: https://daily.dev/posts/5-mistakes-teams-make-when-scaling-net-applications-jeilk21xw twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: 5 Mistakes Teams Make When Scaling .NET Applications | daily.dev og:description: Scaling .NET applications is often hindered by infrastructure design mistakes rather than application code issues. Five common pitfalls are covered: ignoring... og:url: https://daily.dev/posts/5-mistakes-teams-make-when-scaling-net-applications-jeilk21xw og:image: https://api.daily.dev/og/posts/jEilK21xw.png og:image:alt: 5 Mistakes Teams Make When Scaling .NET Applications 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. # 5 Mistakes Teams Make When Scaling .NET Applications **[Telerik](https://daily.dev/sources/telerik)** · 6 min read · 5 upvotes · 0 comments ## Summary Scaling .NET applications is often hindered by infrastructure design mistakes rather than application code issues. Five common pitfalls are covered: ignoring session affinity when adding nodes (which can overload specific instances), using naive round-robin load balancing that ignores node health and request complexity, failing to implement load shedding when systems are overwhelmed, lacking visibility into how requests are actually routed across nodes, and treating load balancing as an afterthought with default settings. The recommended approach involves stateless service design with shared session storage, health-aware routing, intentional request rejection under overload, per-instance metrics collection with request tracing, and proactive application-aware load balancing strategies. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### why does session affinity cause uneven load on my scaled application's servers Session affinity ties all of a user's requests to the server holding their session data, so if usage is uneven across active and inactive users, one instance can become overloaded even while others sit idle. It also means losing that instance drops the sessions bound to it. The fix is designing stateless services and storing session data in shared storage instead of instance memory. _Teams debugging uneven load under session affinity can find infrastructure deep dives like this on daily.dev._ ### what is load shedding and when should a load balancer use it Load shedding is deliberately rejecting some incoming requests so that a system stays healthy under overload, rather than accepting every request and degrading service for everyone. It works like a restaurant pausing new seating so the kitchen can catch up: refusing some requests keeps the ones that get through serviced properly, instead of letting every request suffer. _Anyone designing resilient load-balancing strategies can track patterns like load shedding on daily.dev._ ## Similar posts on daily.dev - [How to Scale a System from 0 to 10 million\+ Users](https://daily.dev/posts/how-to-scale-a-system-from-0-to-10-million-users-ytm2sqndw) · Hacker News · 2 upvotes · 0 comments - [Scale from zero to million users on Azure](https://daily.dev/posts/scale-from-zero-to-million-users-on-azure-cqckvybko) · Tech World With Milan · 21 upvotes · 1 comments - [Things that I Only Learned After Scaling: Non-Obvious Lessons from Production](https://daily.dev/posts/things-that-i-only-learned-after-scaling-non-obvious-lessons-from-production-l1nb2kxhd) · Faun · 0 upvotes · 0 comments - [Designing Systems That Don’t Break When It Matters Most](https://daily.dev/posts/designing-systems-that-don-t-break-when-it-matters-most-ihqyerzu0) · SD Times · 1 upvotes · 0 comments --- Tags: [#authentication](https://daily.dev/tags/authentication), [#.net](https://daily.dev/tags/.net), [#observability](https://daily.dev/tags/observability) [View this post on daily.dev](https://daily.dev/posts/5-mistakes-teams-make-when-scaling-net-applications-jeilk21xw) ```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":"5 Mistakes Teams Make When Scaling .NET Applications","url":"https://daily.dev/posts/5-mistakes-teams-make-when-scaling-net-applications-jeilk21xw","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/5-mistakes-teams-make-when-scaling-net-applications-jeilk21xw"},"datePublished":"2026-07-10T17:58:20.366Z","dateModified":"2026-09-14T09:03:49.181Z","description":"Scaling .NET applications is often hindered by infrastructure design mistakes rather than application code issues. Five common pitfalls are covered: ignoring...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f4483c25145e5d6cee4a5ab77d1597ec?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/f4483c25145e5d6cee4a5ab77d1597ec?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Telerik","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":"Telerik","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/5ee6d4bef8ac4f84886d06f5881963e7","url":"https://daily.dev/sources/telerik"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/5-mistakes-teams-make-when-scaling-net-applications-jeilk21xw","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"authentication,.net,observability","timeRequired":"PT6M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Telerik","item":"https://daily.dev/sources/telerik"},{"@type":"ListItem","position":3,"name":"5 Mistakes Teams Make When Scaling .NET Applications"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/5-mistakes-teams-make-when-scaling-net-applications-jeilk21xw#faq","mainEntity":[{"@type":"Question","name":"why does session affinity cause uneven load on my scaled application's servers","acceptedAnswer":{"@type":"Answer","text":"Session affinity ties all of a user's requests to the server holding their session data, so if usage is uneven across active and inactive users, one instance can become overloaded even while others sit idle. It also means losing that instance drops the sessions bound to it. The fix is designing stateless services and storing session data in shared storage instead of instance memory. Teams debugging uneven load under session affinity can find infrastructure deep dives like this on daily.dev."}},{"@type":"Question","name":"what is load shedding and when should a load balancer use it","acceptedAnswer":{"@type":"Answer","text":"Load shedding is deliberately rejecting some incoming requests so that a system stays healthy under overload, rather than accepting every request and degrading service for everyone. It works like a restaurant pausing new seating so the kitchen can catch up: refusing some requests keeps the ones that get through serviced properly, instead of letting every request suffer. Anyone designing resilient load-balancing strategies can track patterns like load shedding on daily.dev."}}]} ```