Invoke the respective Apigee SaaS Back-end (Proxy) based on incoming Client

Hi,

Listing current high level scenario.

NGINX (Centralized Façade) --- > Apigee SaaS --- >Banckend Apigee Proxies (eg 3 backend Apigee proxy).

Per above listed scenario where Apigee SaaS need to invoke the required Apigee backend proxy based on the respective incoming clientX request.

Say ClientX invokes Centralized Nginx which in turn invokes ApigeeSaaS for any request, which need to invoke the particular Apigee Backend proxy based on the Client which invoked.

(Listed the High level Scenario)

NGINX has the logic of which client invoked the NGINX (like either Client 1 or Client 2 or Client 3 etc invoked it .. ) based on ClientX, need to invoke the respective Apigee Proxy backend (Like Apigee SaaS Proxy1. Or Apigee SaaS Proxy2 or Apigee SaaS Proxy3 etc).

Example, say Apigee SaaS which have 3 backends proxies respectively for each clients (1 to 3), where ApigeeSaas need to invoke respective clientX proxy based on respective clientX request.

How do we achieve this ? like one of option having Header in NGINX (with details about which client invoked the NGINX which gets transferred to ApigeeSaaS and based on Header information Apigee SaaS will invoke the respective backend (Apigee Proxy).

Do we have any other option to suggest, in case if you have used similar design scenario/flow into your system ?

0 1 126
1 REPLY 1

Conditional routing to targets can be achieved through headers or query parameters or something in the payload that can identify the caller(client1, 2 ,3 etc) to route to the appropriate backend using route rules