Hi Piyush, OrientDB Studio will work if you're loading the orientdb-server-config.xml from your embedded app at startup of OrientDB.
Have you seen this documentation on JPA? http://orientdb.com/docs/2.0/orientdb.wiki/JPA-Configuration.html There's also some talk of it in the Object database API documentation: http://orientdb.com/docs/2.0/orientdb.wiki/Object-Database.html The RAM cache to heap space is usually 5:1 to 10:1. http://orientdb.com/docs/last/Performance-Tuning.html Best regards, -Colin On Wednesday, May 6, 2015 at 4:09:39 AM UTC-5, Piyush Katariya wrote: > > Awesome ! Thanks Colin > > Few more queries... > > Is it possible to access orientdb studio in this config ? > By ODM. i meant Object Data Mapper is it any native or 3rd party library > available for OrientDB ? or Object Relation Mapper API like JPA ? > What are recommendation around % of RAM to be reserved for cache use to > ensure overall optimum resource usage ? > > > On Wednesday, May 6, 2015 at 2:35:11 AM UTC+5:30, Colin wrote: >> >> Hi Piyush, >> >> >> 1. Yes. >> 2. The database will still be running as a server, you'll just have >> more control (responsibility) when it's embedded alongside your own Java >> code. >> 3. It's best to let OrientDB use a lot of RAM for its disk cache. >> This will provide the greatest performance. Changes can be synchronized >> across all nodes. >> 4. OrientDB scales very well, but as with all systems, it depends >> greatly on your data model design. With Cassandra, its constraints >> dictate >> your data model design much more than OrientDB does. >> 5. We use and recommend Oracle's Java 8. >> 6. OrientDB does have an Object database API, but the Graph and >> Document APIs are preferred. >> 7. I'm actually not sure about the current status of >> spring-data-orientdb. >> >> -Colin >> >> Orient Technologies >> >> The Company behind OrientDB >> >> On Tuesday, May 5, 2015 at 11:20:09 AM UTC-5, Piyush Katariya wrote: >>> >>> Hello everyone, >>> >>> I am doing the high level POC stuff on TitanDB , ArangoDB and OrientDB >>> to figure out most resilient of them with nice query API support and low >>> latency throughput >>> >>> I have several queries about OrientDB 2.0.9 when used in document mode >>> >>> I will be using it with Spring framework 4.1 with JDK8. >>> Database will be in embedded mode and will use plocal store for max >>> performance as mentioned in guidelines >>> So app code and db share same JVM(s) >>> i will have around 8 GB of RAM of each server >>> >>> 1. Is it possible to have multiple nodes with multi master config and >>> distributed ACID transaction? >>> 2. what other features I might miss compared to Server mode. >>> 3. how much benefit would i get by using RAM as cache. what options are >>> available to synchronize changes across all nodes in cluster. >>> 4. Does Orientdb scales linearly in terms of read and write like >>> Cassandra (TitanDB) >>> 5. Is it thoroughly tested on JDK 8 or still there might be some >>> caveats >>> 6. Any ORM/ODM layer which will make life easier ? >>> Is spring-data-orientdb mature enough to be adopted for given version ? >>> >>> Thanks, >>> Piyush Katariya >>> >>> >>> >>> >>> >>> >>> >> -- --- 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.
