[[["이해하기 쉬움","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-09-04(UTC)"],[],[],null,["# Backing Services\n\nBacking services are any processes that the App contacts over the network during its operation.\nIn traditional operating systems, these services could have been accessed over\nthe network, a UNIX socket, or could even be a sub-process.\nExamples include:\n\n- Databases (e.g. MySQL, PostgreSQL, Cloud Spanner)\n- File storage (e.g. NFS, FTP, Cloud Filestore)\n- Logging services (e.g. syslog endpoints, Cloud Logging)\n- Traditional HTTP APIs (e.g. Google Maps, WikiData, Parcel Tracking APIs)\n\nConnecting to backing services over the network rather than installing them all\ninto the same machine allows developers to focus on their App, independent\nsecurity upgrades for different components, and flexibility to swap implementations.\n\nBacking services in Kf\n----------------------\n\nKf supports two major types of backing services:\n\n- Managed services\n - These services are created by a service broker and are tied to the Kf cluster\n- User-provided services\n - These services are created outside of Kf, but get bound to it externally"]]
