Published in


Global Load Balancer 🌎

What is Global Load Balancing?

Web traffic management and application delivery through several data centers and/or public or private clouds in diverse geographical locations are referred to as global server load balancing (GSLB). Client requests are normally forwarded to closer servers to guarantee minimal latency and maximum speed, and application load is typically controlled by “local” load balancers at each site.

Photo by NASA on Unsplash

How does Global Load Balancing work?

Let’s take a look at what happens when a client sends an HTTPS request to a website that employs global server load balancing. Initially, the main server obtains the client’s IP address and analyzes data about the client’s location. Simultaneously, the server performs health checks to evaluate the servers’ real-time performance and responsiveness. Finally, the main server passes the request to the nearest geographically or with the quickest response time local DNS server. All of this happens behind the scenes in a matter of seconds. The main idea can be seen in the picture below.

Photo by Donna Toomey on EdgeNexus


The main goal of the implementation of global server load balancing (GSLB) is to pursue the main benefits such as performance, maintainability, and disaster recovery.

Performance — by routing user queries to the nearest servers, network latency and problems are reduced. GSLB guarantees that clients in geographically dispersed places receive optimal website or service performance.

Maintenance — data center migrations and upgrades may be carried out without causing any disruption to clients since client requests can simply be diverted to other servers.

Disaster recovery — the high availability of applications reduces the effect of data center or network failures. For example, ff a power outage occurs in California, the load balancer will divert client requests to other servers located across many sites that are geographically separated.

Where are our data centers?

DecisionRules automatically scale performance within a single location and can rapidly reroute requests to the nearest site in the case of a failure.

Locations of DecisionRules actual and future data centers

We have currently 5 data centers locations all over the world in the following locations in: (Central Europe), US East (N. Virginia), US West (Oregon), Brazil (Sao Paulo), and Australia (Sydney).

By the end of Q1 2022, we will have 3 additional ones in the UK (London), India (Mumbai), and South Korea (Seoul).

To find out more, check our documentation or visit us at to try out the modern rule engine. Should you have any further questions or demo inquiry contact us at

Thank you for reading,

Team 🚀

We offer an agile rule engine to let you create, edit and deploy business rules, while all rules run in a secure and scalable cloud. Unlike other rule engines, you can create your first rule in 5 minutes and make 100k decisions in a minute via API.

Recommended from Medium

Meet our first .Net Developer

Create a high availability Infrastructure using AWS CLI

Top things to keep in mind while deploying a Rails app to production?

More than a Hackathon to me — Ivana Dilparic

Autumn Vacancies Digest 👀

Terra Delegation Program 2021 Disbursement 3: Applications

Factors Making Flutter A Favorite Among Businesses

AWS ECR Creation using Terraform

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store

Business rule engine that lets you create and deploy business rules in a secure and scalable cloud.

More from Medium

What is a “Camunda Champion”

Introducing dreiAttest — fraud protection without disrupting the user experience

Taking the next step towards digital transformation with a branded access app (Part 1 / 4)