Backing services are any processes that the App contacts over the network during its operation.
In traditional operating systems, these services could have been accessed over
the network, a UNIX socket, or could even be a sub-process.
Examples include the following:

- Databases---for example: MySQL, PostgreSQL, Cloud Spanner
- File storage---for example: NFS, FTP, Cloud Filestore
- Logging services---for example: syslog endpoints, Cloud Logging
- Traditional HTTP APIs---for example: Google Maps, WikiData, Parcel Tracking APIs

Connecting to backing services over the network rather than installing them all
into the same machine allows developers to focus on their App, independent
security upgrades for different components, and flexibility to swap implementations.

## Backing services in Kf

Kf supports two major types of backing services:

- **[Managed services](https://docs.cloud.google.com/migrate/kf/docs/2.9/how-to/managed-services):** These services
  are created by a service broker and are
  tied to the Kf cluster.

- **[User-provided services](https://docs.cloud.google.com/migrate/kf/docs/2.9/concepts/user-provided-services):**
  These services are created outside of
  Kf, but get bound to it externally.