Best practices and methods for modeling a reusable API,How to design an API for reusability between multiple internal applications
What are some best practices and recommendations to approach building a reusable internal API for use on intra-net applications. We are trying to build a single-source of truth for Employee data (our users). This API should be reused by as many applications as possible to allow them all to be in-sync for Employee Data. This will include Metadata like Addresses, but also relationships such as, ReviewerOf <another Employee>, LeaderOf <Office>, etc.
Are there best practice and/or methods for developing a schema and structure so the API is not overly specialized and/or too generic to be useful?
Thanks
If you want to create reusable apis, then you can use proxy chaining. In proxy chaining, the proxies deployed in the same environments can be called internally within apigee without going full request flow from outside of apigee. Access-control policy will help to use the proxy in your intranet.
