Hi all! I'm researching OrientDB as a potential storage technology for high load website which is going to have millions of users every day. Website provides recommendations and mostly read only.
I was thinking about using OrientDB JPA implementation when noticed that OJPAEntityManager which is implementation of JPA EntityManager interface creates new ODatabaseDocumentTx instance every time it is created. My understanding is that ODatabaseDocumentTx is a connection to OrientDB database and as such it is not lightweight resource and should be pooled in the same way as regular JDBC connections. My question is that is it a good idea to use OrientDB JPA for high load website or I should go with document/graph API and use OPartitionedDatabasePool as connection pooling solution? Thanks, Andrey Verbin -- --- 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.
