Community APIs implement a modular license mechanism that enables additional features. One of these is the asynchronous write module which enables the user to trigger an asynchronous request to create or update an entity. An asynchronous request means that the requester does not need to wait for the process to complete and return a result, instead the request is queued and an operation identifier is returned. This ID can be used to request the status of the operation.
The advantages of an asynchronous request are that write requests can be handled when ACP is down and resources can be managed when there is a high volume of requests.
This course will cover the extended CAPI architecture that enables asynchronous write in CAPI, the flow of data, and how to make asynchronous requests and monitor the progress of an operation. This is a self-study course comprising videos and interactive exercises. At the end of it you will understand how, why and when to use an asynchronous write request.
Upon successful completion of this course every participant will:
Describe the advantages of CAPI asynchronous write
Explain some use-cases for asynchronous write
Name and describe the components which are added to the CAPI architecture to enabale async write
Describe the flow of data when an async request is made
Make an async write request
Use the operation endpoint to request the status of an operation
Monitor processes and messages in the dashboard
Participants should have knowledge of the Avaloq Banking System and an understanding of Avaloq concepts, including the object model, DDICs and Community APIs