Catalog Browse facilitates building out the complex catalog hierarchies and hydrating appropriate data from other services for commerce requests. This is done to minimize the number of requests the caller needs to make and to simplify its knowledge of the complex entity and microservice relationships. Thus, Catalog Browse itself does not maintain persistent stores for the catalog and related data, but coordinates building and hydrating it with other services.
Communication with these other services is handled by integration hook-points called "providers", which are listed below:
Additional providers can be added for additional data hydration such as an InventoryProvider
to hydrate inventory data or a ReviewsProvider
for user review data.