Financial services - BR

Axway Status Review

Issue link: https://axway.uberflip.com/i/1488857

Contents of this Issue

Navigation

Page 4 of 6

5/7 2 Proposed Solution The main objective of this proposed solution is to reduce the risk of this api in impact the environment performance. 2.1 Initial Assumptions The initial drivers for this new solution are: • Reducing the apim policy complexity by reviewing the status api script. • Enabling the integration with backend status end point. For this, we are considering the following solution assumptios: • Each backend api should have a helthcheck method. (e.g. accounts/healthcheck), that should return the current status for this api (e.g. HTTP 200 – it is ok, HTTP 500 – failure). • Moving the healthcheck functionality from policy script to a JavaScript backend to get the general availability for each backend api. 2.2 Status Backend API This backend based on JavaScript API, will get the information for all the configured apis, using each hatcheck method. We have a high-level diagram below: © Axway, 2022

Articles in this issue

view archives of Financial services - BR - Axway Status Review