PuppyGraph is a virtual graph and not a real graph data model. However, at some point in time, once we freeze this as the graph and the graph data model, we would like to extend to a proper graph, mainly because some of the attributes in the source will change over a period of time. We would like to maintain the historical data. Therefore, once we build a virtual layer, we need a real concrete graph layer. PuppyGraph has not provided the concrete graph layer or a mechanism by which we can build our own concrete layer on top of the virtual layer. This functionality will be needed if we have to keep the investment on PuppyGraph after we discover what attributes we need. If we need to continue with PuppyGraph, we need a compelling reason. It has to be extended with a real graph database solution. PuppyGraph could be improved because at some point in time, it always connects to the source system, which means that the source system will always be overloaded because it is a virtual graph. At some point in time, we should be able to decide to bring in the data, but PuppyGraph does not have the support for it. It always depends on the source. The source systems are overloaded once we finalize the graph. PuppyGraph does not have a real native engine for a graph. It has to be extended with a native engine for a graph in the future.
