Service - Catalog Graph: Difference between revisions

From Izara Wiki
Jump to navigation Jump to search
No edit summary
 
Line 9: Line 9:
= Different Catalog, Category Tree, and Category Handler services =
= Different Catalog, Category Tree, and Category Handler services =


The idea currently is they all share the same catalog graph, all different handler services need to add a catalog, categoryNode, and category vertices into this graph, but can have per handler specific handling of the data.
All share the same catalog graph database, the different handler services add standardized catalog, categoryNode, and category nodes into this graph, but can have per handler specific handling of data if needed.


So for example a new Catalog, Category Tree, and Category stack would still enter catalogIds and categoryIds into this graph and the new Category Tree would have it's own nodes linking these to make a graph of relationships, it is up to the Category Tree service to restrict which types of eg categories it will allow added to its tree.
So for example a new Catalog, Category Tree, and Category stack would still enter catalogIds and categoryIds into the graph and the new Category Tree would have it's own nodes linking these to make a graph of relationships, it is up to the Category Tree service to restrict which types of eg categories it will allow added to its tree.


Because all catalogs and categories are added to the one tree we can use this tree to List or search through all categories as long as the filtered properties exist.
Because all catalogs and categories are added to the one tree we can use this tree to List or search through all categories as long as the filtered properties exist.

Latest revision as of 14:39, 16 May 2021

Overview

Deploys an instance of Service - Graph Handler to manage graph database for Service Stack - Catalog

DynamoDB Config table

...

Different Catalog, Category Tree, and Category Handler services

All share the same catalog graph database, the different handler services add standardized catalog, categoryNode, and category nodes into this graph, but can have per handler specific handling of data if needed.

So for example a new Catalog, Category Tree, and Category stack would still enter catalogIds and categoryIds into the graph and the new Category Tree would have it's own nodes linking these to make a graph of relationships, it is up to the Category Tree service to restrict which types of eg categories it will allow added to its tree.

Because all catalogs and categories are added to the one tree we can use this tree to List or search through all categories as long as the filtered properties exist.