Thank you, Scott. It didn't make any sense to me either but I wanted to have another opinion or basically know, if there was any situation where you'd want one cluster for one record [?!?]
Tx, Mihai On Thursday, March 31, 2016 at 2:14:51 PM UTC+3, scott molinari wrote: > > I think of clusters and classes like this. > > A class is only a logic container for data. The cluster, however, is a > logical location for the data. (Someone from ODB correct me, if my thinking > is wrong). > > It makes no sense whatsoever to have a cluster per instance/record. > Though, I am also not completely certain what you mean with the instance > part. > > In the end, you can use clusters for data locality within your server > cluster. This helps, for instance, when your userbase is global and your > database becomes large and you want to spread the data across the globe. > Though, these kinds of contemplations come very late in a scaling out > scenario. > > 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.
