User bio
404 bio not found
Member since Mar 26, 2019
Posts:
Replies:

if you DB is expected to be big, I would invest on optimizing the storage in classes/globals:
- use proper datatype in classes (e.g. save dates as +$H not string "yyyy-mm-dd")
- if there are relationships, plan them carefully, with proper indices.
 - if there are repeated string, use referential tables, do not store them "flat" in the main table
- if there are array/list properties, mane the storage sub-global name very short
All those will reduce I/O, gives a better use of cache buffers, smaller storage footprint and will result in overall performance improvement.  

If you need the API response for the BP logic, then you may increase the BP pool size and use sync call to API. Otherwise, you may use an async call to another BO that do the API call, and update the results later on.

The primary tool is the "Message Viewer" in Interoperability (Management Portal). Click on "Visual Trace" to get the full message lifecycle from end to end with precises timings for each component.
 

Certifications & Credly badges:
Followers:
Following: