service-boundaries
Keep the boundary between services, and between a service and an outside partner, explicit - own your data, map foreign payloads once, keep raw bodies for replay, and test the contract. Use when writing or reviewing code that calls another service or a third-party API, handles a webhook, reads another service's data, or puts deployment topology in a repository.
Pinned to revision 8cad1e4eb680, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.