Persistence using IRule

Our app is stateless. We don't want to tie a user to one server unless OneConnect on all connections through the VIP is required.

 

Our normal web traffic is stateless coming in to multiple virtual directories (ASP.NET applications) behind the same VIP...we are creating a new streaming handler that will get specific calls handed to it based on the URI that was sent to the handler-configured virtual directories.

 

The streaming request we would like to tag/persist to one web server so when it gets cut and reconnects, we reconnect to the same server in the pool so that it's subscription keys of the feed are still valid to a down-stream server (without that down-stream server needing to be told a different web server to publish to for that key/subscriber)

 

 

We use header based pool selection without OneConnect today (different VIP/app)...stateless requests...these requests pass a client identification header that we look at then look up a data group list value to determine which pool to send the request to, then the pool has Observed (member) as it's algorithym...we process well over 350 request/sec with less than 30ms latency on the networking gear (LB, switches, etc) so we're pretty happy with the iRule setup (without it using OneConnect).

 

 

So, unless OneConnect is required for setting up server sticky/persistence, we'd rather not use it...we don't know much about it though (other than it pools sever-side connections) so I'm open to learn more about it if that's the solution we need to go with.