An API exposes a responsibility that another system can rely on. A useful boundary follows a stable business capability rather than the current arrangement of database tables. Internal storage can then change without requiring every caller to change with it.
InterfacesInterfaces
Interfaces and recovery plans that survive ordinary failures.
An interface change is compatible only relative to the clients that use it. Adding a field can still break a strict parser, and adding an enum value can break an exhaustive switch. Compatibility needs evidence about real client behaviour.
InterfacesPagination divides a large result into smaller responses. If the underlying records change between requests, a caller may otherwise miss a record or see it twice. The ordering and consistency model are part of the interface contract.
InterfacesA request can cross several services before returning a response. Independent generous timeouts at every hop can make the total wait much longer than the caller expects. A deadline makes the remaining budget visible along the path.
InterfacesA webhook lets another system notify an endpoint when something changes. The public endpoint receives input from outside its trust boundary. Authentication, replay handling and input limits are therefore part of the message design, not optional finishing work.
Interfaces