The tuning covered in this chapter will give your SOA Infrastructure the performance boost that is required by the composite applications running on it. However, there are composite application design time considerations that should be addressed, otherwise improperly designed composites may degrade the overall performance regardless of how tuned your infrastructure is. As an administrator, having fundamental knowledge of these design time considerations is recommended.
Over the life cycle of a BPEL instance, the instance with its current state of execution might be saved in the database multiple times. This can incur considerable overhead. There are roughly two cases leading to an instance getting stored in the database:
When the instance is waiting for an event (wait, onAlarm, pick, and so on), the instance is dehydrated to the database. Later when the event happens (alarm expires or the message comes in), the instance is rehydrated and resumes...