How do Morphia, Mongo4j and Spring data for MongoDB compare? [closed]

Closed. This question is opinion-based. It is not 开发者_如何学Ccurrently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 6 years ago.

Improve this question

I'm interested in how to they compare to each other, what's more mature, has more features, better for some use cases.

My own use case is to create a real-time monitoring service (think Chartbeat) but if you can talk about other use cases please do it - after all this Q&A might be of interest for others.

---

Morphia may be the most stable of the three. I have not heard much of Mongo4j lately- probably abandoned. I personally like spring-data because of the hades project... You don't need to implement the DAOs. You just write the interface and spring data automatically provides it to you. However Spring Data Mongodb implementation seems a little buggy in my initial trial. If you have hard dates and is working on a production quality product, probably it is wise to choose Morphia.

---

Morphia is the way to go. Pretty stable, very good Play integration and offers access to all Mongo driver features if you need more torque. Reference resolution, entity embedding are working as expected. You get lifecycle annotations too, which are pretty useful for boilerplate persistence code (timestamps?)

---

https://github.com/impetus-opensource/Kundera/wiki/Kundera-Mongo-performance A performance sheet is compiled over here. Kundera is complete JPA2.0 compliant solution and provide much stronger interface, ease of implement and set of features.

-Vivek

---

Kundera is another alternative if you're looking for ease of development and good performance. It's JPA compliant.