Being a multi-tenant system does not say anything about how much and which data needs to be separated, that depends on specific needs. Does the data need to be on different files, disks, servers, building? Why? Because of querying logic, security, maintability, preformance, scalability reasons?
We can discuss how to fullfill these needs while using OrientDB, but we would have to be specific about the needs: "I need to serve specific data to specific tenant" "I need tenants being able to query their data, without begin able to query data of others" "I need to be able to query data of all tenants, while tenants should be able to query only theirs data" "I need fine grained security control applyable to parts of the graph or subgraph" "I need to place data on different machines, because of security reasons, can I still query them as a whole?" "Will I benefit, performance wise, from placing parts of graph/subgraph on different machine?" "Can I maintain (backup, log, recover, ...) parts of the single graph?" .... These are different concerns all applicable to multi-tenant systems, achievable by different means and often placing limits on one another. Dne úterý 20. října 2015 6:10:56 UTC+2 scott molinari napsal(a): > > In a multi-tenant system, which this thread is about, the data between > tenants must be partitioned. That is the kind of partitioning we are > talking about. Not a logical differentiation, but rather, physical > separation. > > Scott > -- --- 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/d/optout.
