Scott ... Keep in mind that all nodes inherit from a single V class, and all edges inherit from a single E class. There are also a half-dozen or so system classes as well. All of those would be shared across all of your tenants.
Even if the ODB security model prevents direct access for a user to a given table, it wouldn't surprise me if there are indirect ways to violate tenant separation in your model. At the very least, each user would know what all the other user IDs are, and you'd have to enforce uniqueness across ask tenants. >From a security perspective, I wouldn't recommend it. - Craig - On Oct 20, 2015 00:40, "scott molinari" <[email protected]> wrote: > We are looking at the possible and best ways to do multi-tenancy within a > single database. Let's say a limit of 500 clusters/ classes would be a good > limit per tenant, then you could only host 60 tenants in one database. 32K > clusters/ classes is very limiting from that perspective. > > And just to be totally certain about classes and vertexes and probably the > noobiest question anyone could ask about OrientDB...LOL!.....if I create a > vertex, it is also automatically a class (a child class of V) too, right? > And that class takes up another cluster. > > So, I am correct in saying, the limit on clusters is also a limit on > classes too. Correct? > > 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. > -- --- 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.
