Assembly

A transaction started by the middleware event needs to be completed within the allotted time. The amount of time allotted for the middleware transaction time includes the time the middleware takes to execute custom pre-hook assembly, custom post-hook assembly, and the middleware call itself. Therefore, end users must be cautious when writing custom assembly hooks such that they do not cause any performance bottlenecks when executing the actual middleware call. If the code in the assembly involves processing the files or executing long running transactions, then it is recommended to execute those processes on a background thread, so that the pre- or the post-hook processes do not block the main thread. However, the transactions started on a separate thread (e.g., background thread) are not part of the transaction started on the main thread (i.e., Middleware Event thread). Therefore, the success or failure on the secondary thread does not affect the transaction on the main thread as long as they do not create deadlocks.