A TCP-based GIS streaming service must handle extreme concurrent connection counts from sensors and thick clients with ultra-low latency at layer 4. Which load balancer is the better fit?
Select an answer to reveal the explanation.
Short Explanation
Millions of skinny TCP sockets are an NLB problem—layer 4, connection-heavy, low fuss. Do not force that firehose through HTTP-only front doors.
Full Explanation
Network Load Balancers operate at layer 4 and are designed for extreme connection scale and low latency TCP/UDP workloads such as GIS streaming services. Application Load Balancers excel at HTTP/HTTPS L7 routing, not raw high-connection TCP substitution. API Gateway is an HTTP API front door, not a general TCP socket LB for millions of connections.