In which measure should duplication of resources across APIs be avoided ?
for dynamic resources: APIs may/may not add data retrieved from an external API like a person's given name, family name retrieved from national registry
for code lists (refData): many APIs reuse common ref data or code lists like gender code, marital status, countries
Considerations:
BFF (backend for front-end) pattern tend to combine different data sources tailor-made for a single front-end, with performance benefits (like caching)
reusable APIs that group or aggregate data from many sources for use in a specific business case (e.g. dimona declaration or presence registrations)
back-office APIs exposing an authentic source often limit to just identifiers from external resources, to avoid cascade of changes in the resource's representation
pvdbosch
commented
11 months ago
In which measure should duplication of resources across APIs be avoided ?
Considerations: