Hi, 1 is true only for INSERT operations, but for all the rest (read, update, delete) OrientDB works as a multi-master engine 2 not a this stage
If you use a distributed or single-node database your client (embedded or remote) will see no difference. You can start single embedded instances ( http://orientdb.com/docs/last/Embedded-Server.html) and let them join a distributed cluster if you want. Luigi 2015-05-26 5:49 GMT+02:00 Pinyin <[email protected]>: > Hi, > > I'm trying to scale my application with OrientDB. But there's still some > questions. > > The document says: > > This is defined as "Cluster Locality". The local node is always selected > when a new record is created. This avoids conflicts and allow to insert > record in parallel on multiple nodes. This means also that in distributed > mode you can't select the cluster selection strategy, because "local" > strategy is always injected to all the cluster automatically. > > > 1 OrientDB is still a single-master database in clusters' level, right? > 2 Am I not able to insert to another cluster managed by a remote node at > all? > > I was planning to use a plocal connection with a embedded server to hide > the distributed details, but that doesn't seem possible if I have to find > the master node manually in my code. > > Thanks. > > -- > > --- > 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.
