Tenant data separation is a standard and huge main security concern, when
dealing with cloud computing infrastructure and that same concerns has to
be covered by the database as well. It isn't a specific need, is is a
necessity.
Scott
--
---
You received this message because you are
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
And thinking some more about the user permissions as a way to partition the
user service data, unfortunately that won't work either. The limit of
classes/ clusters would mean a limit on tenants, despite the ability to
partition their vertexes and edges.
Scott
--
---
You received this
Doesn't it already in a way of classes and clusters?
Dne sobota 17. října 2015 10:59:41 UTC+2 scott molinari napsal(a):
>
> Would OrientDB also support graph partitioning in some way, like TitanDB
> offers, through Tinkerpop's Blueprint PartitionGraph?
>
>
With clusters, maybe. When I think about it, you might be right. I am just
not sure how to create a class and a predefined cluster (for the customer)
at the same time. That would need to be possible, to do multi-tenancy.
There is also a limit on the number of clusters, so that also means a
I also just found this in the documentation about graph partitioning.
http://orientdb.com/docs/last/Partitioned-Graphs.html
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
I didn't say it should be used as a solution for multitenancy.
I am just saying it can be used the same way as Tinkerpop's PartitionGraph.
The thing is, one shouldn't partition any GRAPH database, because it's
basically impossible from the nature of graph (well it's possible but one
woudn't
Well, the whole idea of partitioning is to arrive at data separation. So
clearly, if you want a graph to be homogenic, it can't be partitioned.
Reading the ODB partitioning section, partitioning through the user
permissions system sounds like a pretty good answer to the problem. In
fact, for
Would OrientDB also support graph partitioning in some way, like TitanDB
offers, through Tinkerpop's Blueprint PartitionGraph?
https://github.com/tinkerpop/blueprints/wiki/Partition-Implementation
Scott
--
---
You received this message because you are subscribed to the Google Groups
Hi Michael,
there is not general rule, just because it depends a lot on how many
requests per second will every db have, how many data it will contain, how
complex your queries are and so on.
As a rule of thumb, I would not go over a few tens of (small) databases per
instance, just because CPU,
Hello,
For our architecture we are contemplating something like multi-tenancy. In
our approach each tenant would get their own database. When I say
database, I don't mean server. I mean a database within an OrientDB server.
The question is... Is there a best practice way to do this. The
11 matches
Mail list logo
