OneConnect and Persistence for HTTP App

OneConnect won't help you with load distribution if you're using source address persistence. As soon as a user makes a connection to LTM, we're going to make a load balancing decision and create a persistence entry for that user -> server mapping. When the user makes another request, we'll notice they have a persistence entry for that server and we'll choose an idle TCP connection over which to send their request.

 

 

OneConnect's value-add with load distribution is around non-persistence applications. Even if a VIP doesn't have a persistence profile, we'll still create an L4 connection that basically maps them to a server. With a OneConnect profile, the LTM will detach the server-side connection after every single request which means for HTTP traffic, we're load balancing L7 Requests rather than L4 connections.

 

 

Hopefully that makes a bit more sense?