Sometimes service models can become really big if you put all implementations into one big main model. The drawbacks are obvious: the bigger the model becomes, the longer it will take to load or compile the model. Additionally, if multiple modelers are working on the service, the Designer may slow down. One solution is to use Libraries in this case (the other one is to build multiple smaller services). Using libraries, you can split your service implementation into smaller chunks that can be worked on independently. These chunks can be be reused in multiple services and tested separately. Libraries also speed up collaborative development because you can share your libraries with other developers. If you want to learn more about the concept of libaries, refer to the chapters Working With Libraries and Developing and Using Libraries in the Designer guide. |