The objective of FIM is to process requests that can be initiated by various FIM clients such as the FIM synchronization service and the self-service components according to your configured business policies.
By design, each FIM service instance belongs to a logical group that consists of one or more FIM service instances, which is also known as FIM service partition.
If you have only one FIM service instance deployed to handle the all requests, it is possible that you experience processing latencies. Some operations can even exceed the default timeout values that are appropriate for self-service operations.
FIM service partitions can help you to address this issue.
Regardless of whether you have only one or multiple FIM service instances deployed, your current FIM service partition configuration has an impact on how requests and associated workflows are processed in your environment.
The objective of this article is to explain, what FIM service partitions are, what you need to know about architectural components of a FIM service partition and how you can leverage and configure this feature to address latency related issues when processing requests in your environment.
Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation