Does it make sense to create a graph with a very large amount edges between vertices? For example if I have sellers and products as vertices and each net user by buying something adding new edge (a edge from a seller to a product with data and amount properties means that a seller sold a product). Graph could have a few retailers but for each seller there may be tens of thousands edge leading to products. I'm interested in a quick search of suitable edges, and quick movement between vertices like (finding all products sold by the seller) or aggregation (for example find how much has earned the seller by soap selling. Is graph database good for it? Shouldn't I use a relational database? Best regards, Tomek
-- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
