backing service
Any service an application uses over the network, such as a database, cache, queue, mail relay or payments provider.
In more detail
Factor IV of the twelve-factor app: treat backing services as attached resources. The code makes no distinction between local and third-party services; each is reached through a handle in config and can be attached, replaced or detached without a code change. Swapping a local database for a managed one should be a change to one environment variable.
Related terms
- config — Everything about an application that varies between deploys, such as database addresses, credentials and hostnames.
- resource handle — The address and credentials an app uses to reach a backing service, such as a database URL, kept in config.
- database — A program that stores data in an organised way and answers questions about it, such as PostgreSQL.
- managed service — A cloud service where the provider runs the servers, software updates and much of the operation for you, such as a managed database.
Taught in
- Codebase And Dependencies — DevOps & Site Reliability Engineering
- Config And Backing Services — DevOps & Site Reliability Engineering
- Build, Release, Run And Processes — DevOps & Site Reliability Engineering