Chapter 5
Identifying API Boundaries
Total unification of the domain model for a large system will not be feasible or cost-effective.
—Eric Evans, Domain-Driven Design
Every API provides a mental model for how developers will integrate with it to produce the desired outcomes. Establishing the scope and responsibilities of an API also helps guide the design of this mental model, contributing to a more positive developer experience. By borrowing techniques from domain-driven design (DDD) used in identifying bounded contexts, candidate APIs are identified and the responsibility of each API is clearly defined from the artifacts produced in the Align phase (see Figure 5.1).
Figure 5.1 The first step in the Define phase is to identify API boundaries. ...
Get Principles of Web API Design: Delivering Value with APIs and Microservices now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
