Good Practice in terms revoking multiple backends in sequence

Not applicable

Hello All,

I have the requirement to do the following:

1. Get the data from Vault

2. Use the data and hit a backend.

To do so, what should be the ideal method out of the following two approaches:


Approach 1:

1. From the Proxy, call a Service CallOut to hit a node.js code, which in turn would use the apigee access modules to get the data from the Vault.

2. Use data received in step 1 and hit the backend as defined Target Server config


Approach 2:

1. Use the Target Server Config to hit the node.js code, which in turn would use the apigee access modules to get the data from the Vault.

2. Use data received in step 1 and hit the backend as service callout.

Which approach do you suggest me to select here ?

0 2 232
2 REPLIES 2

Former Community Member
Not applicable

My preference is *Approach 1*. You probably meant it, but I'd call it out explicitly. The service callout should be via proxy chaining. That node.js proxy now becomes a reusable proxy that can be invoked by other proxies.

Hi @MEGHDEEP BASU An alternative approach would be to have a node.js proxy that can do both these steps. This will have some performance benefits & metering will also be easy. Have you thought about this approach?