Direct hundreds of clients to 10's of pools by URI
www.website.com/customer1
They get redirected to:
pool1.website.com/customer1
Customer 2 hits:
www.website.com/customer2
They get redirected to
pool13.website.com/customer2
I would like to handle all of this within the F5 is possible instead of handing them off to individual VIP's mapped to pools. Is it possible to do this:
1) Have the customer hit a single URL (example):
www.website.com/customer2
2) Lookup their pool association from a "routing" table that is populated from an external datastore (example):
customer1 pool1
customer2 pool13
customer3 pool4
.
.
.
3) Direct traffic to the pool based on decision in 2)
If this IS possible, is it better to "cache" the customer routing data in a table locally on the F5? How would I poison that data if I move a customer to a new pool?
I know this is kind of an architecture question, but I figured I'd start at what the iRule is capable of doing before going any farther.