I came across OrientDB a week ago, while looking for a Document DBMS that could be embedded in a client side application. Sadly haven't had time to fully check it out yet, but it looked the most promising of the options out there. The Java/Hibernate pattern seems to be common for java applications, but there's doesn't seem to be (as far as I can see) for a document/object based alternative. I'm currently working with…
There are a ton of JSON stringifications libs for Java, some of which can handle complex object graphs (circular dependencies, etc.). Have a look at Google GSON. Once you can turn your jobs into JSON strings and vice versa, persisting them in a document store should be trivial.
OrientDB: A new Open Source NoSQL DBMS
11–14 of 14 posts
Re: OrientDB: A new Open Source NoSQL DBMS
#12Earlier quoted context omitted.
why would anyone use a young project (with only one developer?) rather than something really well supported like MongoDB or Cassandra I don't know either of the systems you mention - and should have a look into them. I have some experience with couchdb. I've got an app in mind, and have some experience with couchdb but not with the systems you mention. Orient interested me because I'm constantly on the lookout for so…
Have a look at Riak. It scales up (and down) very well. And it's been in production use for a while now.
Re: OrientDB: A new Open Source NoSQL DBMS
#13Earlier quoted context omitted.
Have a look at Riak. It scales up (and down) very well. And it's been in production use for a while now.
Thanks. I've had a look and from what I can see insertion is by HTTP or JSON only, and not over persistent connection. I expect this will be too slow for the volume of data I have.
Re: OrientDB: A new Open Source NoSQL DBMS
#14It looks interesting enough, and the sort-of SQL language looks OK, but I have to ask: why would anyone use a young project (with only one developer?) rather than something really well supported like MongoDB or Cassandra? That said, interesting looking work.
why would anyone use a young project (with only one developer?) rather than something really well supported like MongoDB or Cassandra I don't know either of the systems you mention - and should have a look into them. I have some experience with couchdb. I've got an app in mind, and have some experience with couchdb but not with the systems you mention. Orient interested me because I'm constantly on the lookout for so…