예를 들어 KVM을 사용하여 사용자가 로그인할 때 사용자 세션 데이터를 저장하고 사용자가 로그아웃할 때 이 데이터를 삭제합니다.
속성 집합을 사용하는 경우
다음의 경우에 속성 집합을 사용하는 것이 좋습니다.
키와 값이 설계 시점에 알려져 있는 경우입니다. API 프록시가 실행 중인 경우 API 프록시로 속성 집합 값을 변경할 수 없습니다. 키와 값은 프록시 흐름에서 읽기 전용 변수로 사용할 수 있습니다.
몇 개부터 수백 개의 키(총 110KB 미만)가 있는 경우입니다. 속성 세트 키와 값은 항상 메모리에 저장되어 빠르게 액세스할 수 있습니다.
관리자가 API 프록시를 재배포하지 않고도 환경의 속성 집합을 변경할 수 있도록 하려는 경우입니다.
예를 들어 속성 집합은 라우팅 규칙을 저장하는 데 적합합니다. 라우팅 규칙은 값이 대상 엔드포인트 URL인 키-값 쌍입니다. 이러한 값은 일반적으로 환경마다 다르며 환경에 배포된 여러 API 프록시에서 공유될 수 있습니다. 또한 속성 세트는 공개 키와 인증서를 저장하는 데 적합합니다.
Kubernetes 보안 비밀을 사용하는 경우
이 옵션은 Apigee Hybrid에만 제공됩니다. 이를 통해 API 프록시는 Kubernetes 보안 비밀에 저장된 데이터에 액세스할 수 있습니다. 이 옵션은 실행 중인 프록시 내에서 저장된 데이터를 메시지 흐름 변수로 사용할 수 있는 속성 집합과 유사합니다. 하지만 데이터는 항상 런타임 영역 내에 유지되며 Apigee 클라우드의 관리 영역으로 설정되지 않습니다.
Kubernetes 보안 비밀을 사용할 수 있는 경우는 다음과 같습니다.
관리 영역에 저장하고 싶지 않은 민감한 정보를 저장해야 하는 경우입니다. 예를 들어 Kubernetes 보안 비밀을 사용하여 외부 시스템에 액세스하는 데 필요한 비공개 키 또는 사용자 인증 정보를 저장할 수 있습니다.
[[["이해하기 쉬움","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-18(UTC)"],[[["\u003cp\u003eApigee offers three primary data persistence mechanisms for API proxy developers: Key Value Maps (KVMs), Property Sets, and Kubernetes Secrets (for Apigee hybrid).\u003c/p\u003e\n"],["\u003cp\u003eKey Value Maps (KVMs) are suitable for storing large amounts of data that changes frequently, accessible and modifiable at runtime through the KeyValueMapOperations policy.\u003c/p\u003e\n"],["\u003cp\u003eProperty 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.\u003c/p\u003e\n"],["\u003cp\u003eKubernetes 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.\u003c/p\u003e\n"],["\u003cp\u003eThe 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.\u003c/p\u003e\n"]]],[],null,["# Accessing configuration data\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\n\nAPI proxy developers commonly use one or more Apigee data persistence mechanisms to store configuration\ndata so they can later access it in an API proxy.\nThis topic discusses how to choose the right persistence mechanism depending on your use case.\n\nPersistence mechanisms\n----------------------\n\nThe following table briefly describes the persistence mechanisms available in Apigee:\n\nScope of persistence mechanisms\n-------------------------------\n\n\nEach of the available persistence mechanisms has a specific scope that determines where you can\naccess its stored data. The following table summarizes the available scopes for each persistence\nmechanism. For more about scopes, see [About persistence scope](/apigee/docs/api-platform/cache/key-value-maps#scope) and\n[Property\nset scopes](/apigee/docs/api-platform/cache/property-sets#scopes).\n\nDeciding which persistence mechanism to use\n-------------------------------------------\n\n\nThis section describes use cases for each persistence mechanism to help you decide\nwhich one is best suited for storing configuration data.\n\n### When to use Key Value Maps\n\n\nApigee does not provide APIs for storing, updating, or deleting KVM data. You must perform these\ntasks using the [KeyValueMapOperations policy](/apigee/docs/api-platform/reference/policies/key-value-map-operations-policy). The policy lets you perform KVM operations at runtime, when the\nproxy is executing.\n\nConsider using KVMs when:\n\n- You have thousands, hundreds of thousands, or millions of key value map entries (any number up to the [documented KVM size limits](/apigee/docs/api-platform/reference/limits)).\n- You have entries that are not known at design time.\n\n\nFor example, use KVM to store user session data when a user logs in and delete it when the\nuser logs out.\n\n### When to use property sets\n\n\nConsider using property sets when:\n\n- The keys and values are known at design time. Property set values cannot be changed by the API proxy when it is running. They are available in the proxy flow as read-only variables.\n- You have a few to few hundred keys (\\\u003c110 KB in total). Property set keys and values are always stored in memory for quick access.\n- You want the convenience of allowing administrators to change property sets in an environment without redeploying API proxies.\n\n\nFor example, property sets are good for storing route rules. Route rules are key/value pairs\nwhere values are target endpoint URLs. These values typically vary between environments and\ncan be shared by multiple API proxies deployed in an environment. Property sets can also be\na good choice for storing public keys and certificates.\n\n### When to use Kubernetes Secrets\n\n\nThis option is only available with Apigee hybrid. It allows an API proxy to access data stored in\nKubernetes Secrets. This option is similar to property sets, where stored data is available\nas message flow variables within the executing proxy. However, the data always remains within the\nruntime plane; it is never set to the management plane in the Apigee cloud.\n\n\nConsider using Kubernetes Secrets when:\n\n- You need to store sensitive information that you never want to be stored in the management plane. For example, you might use a Kubernetes Secret to store private keys or credentials required to access external systems.\n- You need to share stored data with multiple API proxies deployed in the same environment."]]
