Question
T-systems ICT India Pvt Ltd
T-systems ICT India Pvt Ltd
IN
T-systems ICT India Pvt Ltd
Posted: May 31, 2022
Last activity: Jun 1, 2022
Last activity: 1 Jun 2022 1:12 EDT
Closed
Solved
Best practices in Integration- REST API
Hi,
Application is using (Thread Level) Data Pages (with Report Definition as a source) in @ 100 screens.
Now I need to replace source of a Data Page to REST Connector (consuming 3rd party REST Service). Thus calling API @ 100 time in a case.
How does it affects the Application Performance.? How many times can we call API as a best practice ?
Should I create single API for every Data Element instead ?
***Edited by Moderator Marije to change type from Pega Academy to Product, added Product details and Capability tags****
Accepted Solution
Posted: 3 years ago
Updated: 3 years ago
Updated: 1 Jun 2022 1:12 EDT
ING Bank N.V.
ING Bank N.V.
NL
Posted: 3 years ago
T-systems ICT India Pvt Ltd
T-systems ICT India Pvt Ltd
IN
Thank you for your reply.
I will reuse same API through D_Page & Keyed Pages.
Also will group common data in one API.
@VallabhGopalThe performance of the API can depend on a lot of factors (volume of data, frequency of traffic etc), but calling the same API hundreds of times for every single attribute might not be the best approach.
If your data has common elements, then perhaps they can be grouped into a separate API, and called only once through an asynchronous Job scheduler.
Some other options are :
---- Make the API calls in an off-peak hour and storing them in a Data page for usage later.
---- Make the calls once for every operator instead of calling it per thread.
Maybe filling in the below details will help answer this question better :
--- How many fields are we talking about ?
--- Does the API have to called per case ? Does it pass case specific data ?