Now, for the difficult part. We need to know how many partitions, shards, and containers we need to hold a set of data. As we expect the volume of data and clients to grow, we need to support our current load, as well as our load 3-5 years down the road. We just mentioned the end of a deployment. A WebSphere eXtreme Scale deployment can remain active for months and years without a restart. As we would like the grid to remain active for such long periods of time, we need to have the ability to add capacity to it as our needs grow.
We know how to add additional containers to an already running grid. As we have a suggested lower limit of 10 shards per container, and a lower limit of one shard per container, we know the number of partitions we set determines the maximum number of containers our deployment uses:
<objectgridDeployment objectgridName="PaymentProcessorGrid"> <mapSet name="ppMapSet" numberOfPartitions="101" minSyncReplicas="0" maxSyncReplicas="0" maxAsyncReplicas...