I don't program in Java and don't really share the same needs. But, I do have these requirements, which I think OrientDB can fulfill:
Avoidance of the object relational impedance mismatch, which traditional RDBMSes force on a developer and cause agility to become almost impossible The ability to still create relationships and find related data quickly, in documents ACID compliance, only when I need it Transactions, only when I need them The ability to create hierarchical and graph data models and traverse them relatively easily and quickly Fast response times, even for larger data sets Proper web scalability i.e. horizontal scaling Can be used on commodity hardware (i.e. VMs in a cloud computing IaaS) Relatively easy to administer Can take care of decent full text indexing/ searching (from what I am told, the support for Lucene will be advancing) Can support a good number of databases in one server instance. I've read 1000 on one server isn't an issue. 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.
