My main question is whether separate collections affect performance in a positive or negative way. The IMDB example database has everything in one vertices collection with a type with all the relationships in another single collection. I'm leaning towards separate collections per type. For example, PostalCode, City and Business. However, what about Edge collections? The structure in this case would be (PostalCode)->[LocatedIn]->(City)<-[LocatedIn]<-(Business). But should the two types of LocatedIn relationships be stored in separate Edge collections? Is this just a design concern or would it have a performance effect?
I'm also curious about naming conventions. I was wondering if there have been common or best practices that have developed. You know, the Arango version of Pythonic. Arangonish? All lower case with underscores? Camel case? Singular? Plural? I know it doesn't really matter. Just wondering. -- You received this message because you are subscribed to the Google Groups "ArangoDB" 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/d/optout.
