Changes between Initial Version and Version 1 of Ticket #403, comment 3


Ignore:
Timestamp:
26.01.2013 16:13:41 (9 years ago)
Author:
jri
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #403, comment 3

    initial v1  
    55But the main reason for being hesitant with Blueprints is that I'm not fully sure anymore a graph database is the suitable DB for DM. This new view arised from the current work of rewriting DM's storage layer. With the new storage layer we make practical no use of the central graph DB feature -- traversal -- anymore but rely solely on Lucene indexes. This feels more like a key-value store or a columnar database now. For me, this suggests we should investigate and re-discuss the DB question on a rather fundamental level. 
    66 
    7 From my current point of view the new DeepaMehtaStorage abstraction is the suitable main storage interface for DM. Of course there can be a Blueprints implementation of that interface but I would not do it the other way around for the reasons mentioned above. 
     7From my current point of view the new DeepaMehtaStorage abstraction is the suitable main storage interface for DM. Of course there can be a Blueprints-based implementation of that interface but I would not do it the other way around for the reasons mentioned above.