![websocket to tcp bridge subdomain websocket to tcp bridge subdomain](https://cdn.educba.com/academy/wp-content/uploads/2019/12/MQTT-vs-WebSocket.jpg)
![websocket to tcp bridge subdomain websocket to tcp bridge subdomain](https://user-images.githubusercontent.com/79349894/138270841-64f6b6dd-2727-4c30-b363-7e7f33720ee7.png)
Support for Route53 DNS Fail Over: Many times, we have noticed that there are geo catastrophes which might disrupt your business.This is great news for IoT, Gaming, Messaging and AdTech Applications. Long Lived TCP Connections: Network Load Balancer supports long-running TCP connections that can be open for months or years making it ideal for WebSocket type of Applications.It has eased a major boilerplate handling the applications earlier needed to have. Earlier you were needed to get your remote address in application from HTTP header X-Forwarded-For.
![websocket to tcp bridge subdomain websocket to tcp bridge subdomain](https://d2908q01vomqb2.cloudfront.net/1b6453892473a467d07372d45eb05abc2031647a/2018/12/18/websockets-arch.png)
Source/Remote Address Preservation: With Network Load Balancer, the original source IP address and source ports for the incoming connections remain unmodified.If something in that particular Availability Zone fails, AWS will automatically switch-over the traffic to other healthy Availability Zones. This gives you a great flexibility in isolating application that shall work within particular Availability Zone. Zonal Isolation: The Network Load Balancer can be used for applications architectures lying with a Single Zone.You can also use Elastic IP to assign fixed IP address for each Availability Zone. Classic Load Balancer posed a limitation here. The greatest advantage is when you need to whitelist your application within a firewall of a customer or partner, you can easily do so now. Classic Load Balancer used to provide a URL endpoint which you were mapping with CNAME DNS Record to create a subdomain. Static IP Addresses: Each Network Load Balancer provides a single IP address for each Availability Zone.Let’s look at its feature set to understand how you can utilize it. It operates at OSI Layer 4(Transport) that can handle millions of requests per second while maintaining high throughput at ultra-low latency. AWS recently announced a new Load Balancer called as Network Load Balancer(NLB).