Multai Load Balancer Introduction
Multai is a light, software-based Layer 7 load balancer designed from the ground up specifically to provide a seamless experience, detailed insights, simplified management and scaled load balancing – regardless of the cloud infrastructure your applications run on. MLB also supports hybrid deployments, meaning you can have MLB load balancers located on-prem, in AWS, GCP, and Azure all at the same time.
- Runtime Node: A node (VM or Server) which runs the MLB “Go” binaries and acts as the Proxy between incoming traffic and application servers. These Runtime nodes can be launched either On-premise or in your Cloud provider. Once your hosts are launched you can start creating Load Balancers using the UI console or via API.
- Runtime Deployment: A set of Virtual or Physical Machines running the MLB Software called “Runtime Nodes“.
- Balancer: A load Balancer is an entity that acts as a reverse proxy and distributes network or application traffic across a number of servers.
- Listener: A process that checks for incoming connections in a specific protocol to port to the Load Balancer.
- Routing Rule: Rule that matches an incoming request and forwards it to a TargetSet for Target selection. This can be based on HTTP Header or based on an expression that matches the request, e.g. Path(“/v1/path”).
- Target: The final destination of the incoming request, each target is defined by
URL <protocol>://<host>:<port>, e.g. http://172.31.10.13:5000 and weight.
- Target Set: A logical collection of Targets that get traffic from a Routing Rule.