Backing services
Backing services is part of the original 12 principles. All backing services should be treated as bound/attached resources. A backing service is simply any service that is consumed by an application. A bound/attached resource is simply the connection between an application and a backing service. Some example backing services include data stores (MySQL, S3), caching (Redis), and messaging (RabbitMQ). In essence, an application bound to some backing service should not have code that is specific to that type of backing service. The generic nature of the implementation will enable backing services to attached/detached at will. Such scenarios enable administrators to quickly and reliably replace failing backing services without ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access