Solved: Can APIGEE APIs connect to other APIs? - Page 2

srikanthpogula · 10-09-2023 11:57 PM

Hi,

Currently we have services/Service Layer(services.mycompany.com) built on Sprint Boot which connects to PIM database to get product details and send it to be displayed on a web page. We re-implemented these APIs on APIGEE for better security and response caching. Just in case APIGEE APIs are unable to connect to PIM DB, can the logic be implemented at APIGEE layer to invoke existing Service Layer APIs to get data?

If yes, can someone point me to a documentation?

dchiesa1

oh I see

To be honest I've never seen a design that included Apigee along with a plan to "route around" Apigee in the case Apigee becomes unavailable. Managed Apigee (managed by Google) includes a 99.9 SLA or 99.99 if you opt for multiple regions. It's in the contract. That's pretty good, and probably better than the SLA for most backend systems.

Rather than design the product detail page to have 2 endpoints to invoke, why not .. use caching at the product detail page? Or in a CDN, between Apigee and the product detail page? But in this case, I am of the opinion that "YAGNI" - you aren't going to need it. Cache if you want better performance, but not to protect against upstream service disruption. Rather than assume Apigee will fail, and design accordingly, why not assume Apigee will meet its SLA, and design accordingly? Apigee routinely exceeds the SLA, sometimes by significant amounts. 99.999% is typical. Some customers consistently see 100%. That availability is not contractually guaranteed, but it's common.

If you're managing an Apigee instance on your own, and are concerned about availability, my question is: Why? Let Google manage it for you and let go of the cost and hassle.

View solution in original post