This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Log in to ask a question

Best practice for legacy apps to consume an API

Posted on 08-28-2020 09:01 PM
manimanavalan
New Member
Reply posted on --/--/---- --:-- AM

Hi,

Please suggest the best practice for below scenario.

System of records exposes the functionality through APIs which is hosted in APIGEE platform.

legacy applications interested to consume the functionality but they cannot invoke REST API. Assume that legacy application cannot be modified to make rest API calls.

What is the recommended approach for this scenario?

Existing approach: Integration Servers to pull/push records between legacy system and APIGEE. The flow is, Legacy system <--> Integration Servers <--> APIGEE <--> System of Records.

Problem: In this approach, Apigee has to share the consumer credentials to Integration server which is security issue. Also Apigee is missing the actual consumer metrics for consumption report.

0 2 148
Topic Labels
0 Likes
2 REPLIES 2

Posted on --/--/---- --:-- AM
Not applicable
Reply posted on --/--/---- --:-- AM

Apigee will produce rest api to consume. You have to call via another layer of service. You can use other security features provided by Apigee like oauth2.0 or any other options.

0 Likes

Posted on --/--/---- --:-- AM
manimanavalan
New Member
In response to
Reply posted on --/--/---- --:-- AM

Legacy system & Integration Servers together called as consumer app. This approach is being used today and looking for any other best approaches used in the industry. The concern is, sharing the client id & secret to Integration Servers which is acting consumer app on behalf of legacy system.

0 Likes