API resource identification
The design of the API is tied to the underlying business domain model of the problem domain. The APIs need to be consumer-centric and focus on the needs of the consumer. The domain-driven design principles are applied to identify the right granularity. The bounded context pattern is the central pattern that helps in dividing the problem area into different bounded contexts and being explicit about their relationship. For an enterprise, the resource identification is also driven by the canonical models defined by the central/group architecture teams.
Furthermore, depending upon where the API is defined and what features/functionality it is exposing, APIs can be classified into three, broad categories:
Let's discuss ...
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