Hey @Sachin_Kannaujiya,
We do represent 3d data in a DAG. In that sense, there is no reason why you couldn’t store model data in a neo4j database.
However there are a few things to note:
- many of the object can become quite large in sheer size of the attributes required to represent the object (not to mention textures and other blob like items). Its been a while since i last used neo4j but if i remember correctly, its super good at storing a vast number of objects and their relationships, but its not so happy about storing big object in the nodes ( i might be wrong on this )
- our object models heavily uses the decompisition api, to yield good performance for sending, receiving and storing the objects. Our objects kit specifies how each object is processed and stored. This setup might or might not be compatible with a neo4j based storage layer.
- currently we do not have a javascript / typescript SDK that would implement kits, decomposition api, etc. The closest you can get is with the object loader, but that is still half the story at best.
I am interested, what is your usecase for storing the data in neo4j?