This pattern maps a subset of the data to a single server only. This server can then aggressively cache that data because it knows all requests for that subset are being routed to a single server. The data can be partitioned a number of ways. We can use either a variable set of partitions or a fixed set of partitions.
When using a one of N policy for the partitions, the highly available (HA) manager will activate each partition on exactly one cluster member. This is very useful if an application has some long-lived tasks that would benefit from running only on a single cluster member at a time.