![]() ![]() When designing the Source APIs, it is important to define schema types using primary key(s) that uniquely identify them. This ensures that the customers can continue using the updated functionality without disruption or reliance on other APIs. It is crucial that when a source API introduces changes to an existing feature, these modifications should be seamlessly consumed by customers without any dependency on the merged API. Similarly, the Authors, Reviews, and Users API teams are responsible for independently managing their respective areas of focus. This API empowers users to query book metadata, as well as perform actions such as adding, updating, and deleting books from the catalog. To achieve this, the team manages a dedicated source AppSync API. ![]() Their responsibility is to handle all data related to each book in the site’s catalog. Taking the example shown above, let’s consider the Books API team. Source APIs should be designed to be independent and self-contained, providing a comprehensive solution for a specific use-case. Here, the domain refers to the area of knowledge or business domain in which the software is being developed. Each team owns and maintains the data and APIs based on Domain-driven design.ĭomain-Driven Design (DDD) is an approach to software development that emphasizes understanding and modeling the domain of the problem being solved. Source APIs encompass information about one or more related domains owned by a team. When designing the Source Graphs, think of each source graph as a microservice which handles a single domain, implemented by domain experts that can be developed independently. Source APIs – Think of Types, Unique key(s), Teams, and Ownership
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |