Global Load Balancing
Prophaze load balancing enables organization to be more cost effective by shifting to enterprise grade cloud based solution which replaces their costly appliances. Thus built in flexibility is provided to support a single data center with multiple servers. Real time health monitoring and notifications also helps to ensure that traffic is always routed to a viable web server.
Global Server Load Balancing
High availability and consistent performance of application and website is ensured though Global server load balancing. It is mainly for companies that operate multiple data centers. Prophaze WAF GSLB helps to route traffic to a specific data center by looking for either the best connection time or Geo targeting methods based on the user’s geographical location.
Features
Layer-7 and Layer-4 Load Balancing
Operates at layer-7 and layer-4 load balancing of the Open Systems Interconnection (OSI) model.
HTTP/2 and gRPC Support
HTTP/2 is a new version of the Hypertext Transfer Protocol (HTTP) that uses a single, multiplexed connection to allow multiple requests to be sent on the same connection. It also compresses header data before sending it out in binary format and supports SSL connections to clients.
Our load balancer can route and load balance gRPC traffic between microservices or between gRPC enabled clients and services. This allows seamless introduction of gRPC traffic management in the architectures without changing any of the underlying infrastructure on the customers’ clients or services.
TLS Offloading
This feature enables traffic encryption between load balancer and the clients that initiate SSL or TLS sessions.
Sticky Sessions
Sticky sessions are a mechanism to route requests from the same client to the same target. Global Load Balancers support both duration-based cookies and application-based cookies.
Native IPv6 Support
Global Load Balancers support native Internet Protocol version 6 (IPv6) in a VPC.
Request Tracing
Request tracing allows you to track a request by its unique ID as it makes its way across various services that make up the bulk of traffic for your websites and distributed applications.
Redirects
Global Load Balancer can redirect an incoming request from one URL to another URL. This includes the capability to redirect HTTP requests to HTTPS requests, which allows you to meet your compliance goal of secure browsing, while being able to achieve better search ranking and SSL/TLS score for your site. You can also use redirects to send users to a different web site; for example, redirecting from an old version of an application to a new version.
Fixed Response
Global Load Balancer can control which client requests are served by your applications. This enables you to respond to incoming requests with HTTP error response codes and custom error messages from the load balancer itself, without forwarding the request to the application.
WebSocket’s Support
WebSocket’s allows a server to exchange real-time messages with end-users without the end users having to request (or poll) the server for an update. The WebSocket’s protocol provides bi-directional communication channels between a client and a server over a long-running TCP connection.
Server Name Indication (SNI)
Server Name Indication (SNI) is an extension to the TLS protocol by which a client indicates the hostname to connect to at the start of the TLS handshake. The load balancer can present multiple certificates through the same secure listener, which enables it to support multiple secure websites using a single secure listener.
IP addresses as Targets
Use IP addresses as targets to load balance applications hosted in on-premises locations.
Lambda functions as Targets
Lambda functions as targets for a load balancer and leverage the support for content-based routing rules to route requests to different Lambda functions.
Content-based Routing
If your application is composed of several individual services, an Application Load Balancer can route a request to a service based on the content of the request such as Host field, Path URL, HTTP header, HTTP method, Query string or Source IP address.
- Host-based Routing
- Path-based Routing
- HTTP header-based routing
- HTTP method-based routing
- Query string parameter-based routing
- Source IP address CIDR-based routing
Containerized Application Support
Global Load Balancer provides enhanced container support by load balancing across multiple ports on a single instance.
Slow Start Mode with Load-Balancing Algorithm
Load Balancer supports a round-robin load-balancing algorithm. Additionally, it supports a slow start mode with the round-robin algorithm that allows you to add new targets without overwhelming them with a flood of requests. With the slow start mode, targets warm up before accepting their fair share of requests based on a ramp-up period that you specify. Slow start is very useful for applications that depend on cache and need a warm-up period before being able to respond to requests with optimal performance.