Hi, We're currently developing a project and we're doing tests with *OrientDB* *v1.7-rc2*.
*- Theoretical question:* We could start our website with a single database on a single server. This database could become large very quickly. When the amount of datas will become too large, instead of enlarging the disk capacity, we'd like to add a second server to store all new records. And so on ... Is this the better way to proceed? - If yes, *question about OrientDB:* How to implement this architecture? We've read some articles about the auto-sharing feature (with the config file orientdb-aserver-config.xml) and this tutorial: https://github.com/orientechnologies/orientdb/wiki/Distributed-Routing, but we didn't found any documentation about the way to implement it. Any information would be welcome! Marcel -- --- 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.
