IT Glossary
What is a load balancer?
A digital dispatcher that spreads traffic across several servers so that none of them suffocates and the site stays available.
Black Friday, just after midnight: thousands of customers enter the online shop in the same minute, and if everything leans on a single server, that server gives up precisely while you were selling the most. A load balancer is the dispatcher that divides incoming traffic across several identical servers, much as a supermarket opens extra checkouts the moment a queue forms. It continuously checks which servers are answering healthily and sends visitors only to those; when one fails, the others absorb its share without a customer noticing anything at all. For a business that translates directly into money — the site stays available through traffic peaks, maintenance happens without downtime because servers are updated one at a time behind the dispatcher, and growth is handled by adding machines rather than rewriting the application. It is the component that turns we hope it holds into we know it holds. On managed cloud services it costs a small monthly fee plus processed traffic, which is normally a fraction of the revenue lost to one hour of downtime in high season.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
Availability at traffic peaks
Marketing campaigns and busy seasons stop knocking the site over — load spreads across several servers and the sales keep going through.
Maintenance without downtime
Servers are updated in turn while the balancer routes traffic to the active ones, so customers never meet the site unavailable page.
Growth by adding, not by rewriting
When the business grows you add servers behind the same balancer — a matter of hours, not a months-long re-architecture project.
Frequently asked questions
At what traffic level does a load balancer start to make sense?
Average traffic is the wrong measure; what counts is the size of the peaks and the cost of being unavailable. A shop running aggressive campaigns, or an application your staff depend on every working day, justifies one far earlier than a brochure site with steady, moderate visits and no revenue tied to the minute.
Is a cloud load balancer expensive?
On AWS, Azure or Google Cloud you pay from a few tens of euros a month plus the traffic processed. Set against the revenue lost during a single hour of downtime in peak season, that figure is normally a rounding error rather than a budget decision.
What happens if the load balancer itself fails?
Managed cloud services run the balancer redundantly across several availability zones precisely so it does not become the single point of failure. On self-hosted installations the equivalent is two instances configured with failover between them — worth asking any infrastructure provider to describe explicitly before you sign.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247