[[["容易理解","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-06-28 (世界標準時間)。"],[[["Apigee offers three primary data persistence mechanisms for API proxy developers: Key Value Maps (KVMs), Property Sets, and Kubernetes Secrets (for Apigee hybrid)."],["Key Value Maps (KVMs) are suitable for storing large amounts of data that changes frequently, accessible and modifiable at runtime through the KeyValueMapOperations policy."],["Property Sets are best for configuration data known at design time, such as route rules or public keys, and they are read-only during proxy execution."],["Kubernetes Secrets, available only in Apigee hybrid, are used for storing sensitive data that should not be in the management plane, like private keys or credentials, and are accessible to multiple proxies in the same environment."],["The mechanisms differ in their scope of data access: KVM data can be accessed at the organization, environment, and API proxy levels, property set data can be accessed at environment and proxy level, and kubernetes secrets are only accessible at environment level."]]],[]]