> For the complete documentation index, see [llms.txt](https://docs.vngcloud.vn/vng-cloud-document/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vngcloud.vn/vng-cloud-document/glb/operating-model.md).
# Operating Model
GLB is a critical solution for ensuring the performance and availability of web applications on a global scale. By distributing traffic to the most appropriate servers, GLB helps minimize latency, improve resiliency, and enhance user experience. Below is an example of how GLB operates.
1. Geographic Distribution**:** You deploy your application servers across multiple geographic regions (for example: HCM-03, HAN-01).
2. GLB Configuration**:** You configure a GLB to manage traffic distribution across these servers. The GLB continuously monitors server health and network conditions.
3. User Access**:** When a user enters your website address, the request is first sent to the GLB.
4. Location Identification**:** The GLB determines the user’s geographic location based on their IP address.
5. Server Selection**:** Based on the user’s location and other factors (such as server load and server health status), the GLB selects the nearest and most suitable server to handle the request.
6. Request Routing**:** The GLB then routes the user’s request to the selected server.
**Key Components in GLB Operations:**
* **Geolocation:** The ability to identify the geographic location of users is a core component of GLB.
* **Load Balancing Algorithms:** GLB uses load balancing algorithms to distribute traffic efficiently, ensuring that no server becomes overloaded.
* **Health check:** GLB continuously performs health checks on servers to detect failures and automatically remove unhealthy servers from traffic distribution.
* **DNS:** GLB typically works closely with the DNS system to route requests to the appropriate server IP addresses.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.vngcloud.vn/vng-cloud-document/glb/operating-model.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.