Working with Application Load Balancer (ALB)
Overview
What is ALB?
Application Load Balancer (ALB) is a tool in network and server infrastructure used to distribute network traffic to multiple servers or virtual machines to improve the performance and availability of applications. ALB operates at the application layer, allowing traffic distribution based on many factors such as request type, server state, and load distribution algorithm. ALB provides advanced routing capabilities, allowing traffic to be directed based on Host or Path Header. It also supports session persistence, which helps maintain user sessions to the same server. This is useful for applications that require consistency in user interactions. For more information about ALB, please refer to [How it works (ALB)]
Model:
![](https://docs.vngcloud.vn/~gitbook/image?url=https%3A%2F%2F1985221522-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252F7rE7M1L7GYcwQzNGd0aB%252Fuploads%252FT5l5JIAlNUxm9wx8c0Q5%252Fimage.png%3Falt%3Dmedia%26token%3D66f31fb6-6d9e-4d92-a719-33c1d7d39e3f&width=768&dpr=4&quality=100&sign=829b3115&sv=1)
In addition to the basic components of a K8S cluster and an ALB that you already know, in this model we use:
Ingress: is a resource in Kubernetes that is configured to make Services accessible from outside the k8s cluster via URL, and can also load balance traffic, support SSL/TLS connections and provide virtual hosting based on names. An Ingress does not arbitrarily expose protocols other than HTTP and HTTPS. Ingress acts as a single entry point for HTTP and HTTPS requests from outside the cluster to internal services. Traffic routing is controlled by rules defined in the Ingress resource (Ingress Yaml File). An Ingress is managed by VNGCloud Ingress Controller: is an application that runs in the cluster and manages Ingress resources based on the Ingress Yaml File defined by the customer
Last updated