[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-08-21 (世界標準時間)。"],[[["\u003cp\u003eThis document focuses on how backend system performance impacts API requests routed through Apigee.\u003c/p\u003e\n"],["\u003cp\u003eAPI requests travel from the client, through the Apigee gateway, to the backend system, and then back, making overall performance dependent on both Apigee and the backend.\u003c/p\u003e\n"],["\u003cp\u003eInadequately sized backends can cause API requests to fail due to resource stress during traffic spikes, such as CPU, memory, and load limitations.\u003c/p\u003e\n"],["\u003cp\u003eSlow backends result in increased latency, premature timeouts, and a poor customer experience, even with Apigee's tunable options.\u003c/p\u003e\n"],["\u003cp\u003eCaching and resolving underlying issues in backend servers are best practices to improve API response times and reduce backend load.\u003c/p\u003e\n"]]],[],null,[]]
