some questions about designing on OrientDB
<p>We were looking for the most suitable database for our innovative “collaboration application”. Sorry, we don’t know how to name it in a way generally understood. In fact, highly complicated relationships among tenants, roles, users, tasks and bills need to be handled effectively.</p>

<p>After reading 5 DBs(Postgrel, Mongo, Couch, Arango and Neo4J), when the  words “… relationships among things are  more important than things themselves” came to my eyes, I made up my mind to dig into OrientDB. Both the design philosophy and  innovative features of OrientDB (multi-models, cluster, OO,native graph, full graph API, SQL-like, LiveQuery, multi-masters, auditing, simple RID and version number ...) keep intensifying my enthusiasm.</p>

<p>OrientDB enlightens me to re-think and try to model from a totally different viewpoint! </p>

<p>We are now designing the data structure based on OrientDB. However, there are some questions puzzling me.</p>

<ol>
<li>LINK vs. EDGE</li>
</ol>

<p>Take a case that a CLIENT may place thousands of ORDERs, how to choose between LINKs and EDGEs to store the relationships? I prefer EDGEs, but they seem like to store thousands of RIDs of ORDERs in the CLIENT record.</p>

<ol start="2">
<li>Embedded records’ Security</li>
</ol>

<p>Can an embedded record be authorized independently from it’s container record?</p>

<ol start="3">
<li>Record-level Security</li>
</ol>

<p>How does activating Record-level Security affect the query performance?</p>

<p>Hope I express clearly. Any words will be truly appreciated. </p>