morphia

This is the first time im using the DAO pattern. From what I've read so far, implementing this pattern will help me seperate my calling code (controller) from any persistence implementation - exactly what I want; that is, I don't want to be restrcited to the use of any particular database or 3rd party libraries. I'm creating some test code (in TDD fashion) using MongoDB and morphia (as an example), with morphia's provided BasicDAO class. As far as I can tell, extending BasicDAO<T, V> requires a constructor that accepts Morphia and Mongo objects; these are very specific (3rd party) types that I

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

My database of choice is MongoDB. I'm writing a data-layer API to abstract implementation details from client applications - that is, I'm essentially providing a single public interface (an object which acts as an IDL). I'm testing my logic as I go in a TDD manner. Before each unit test, an @Before method is called to create a database singleton, after which, when the test completes, an @After method is called to drop the database. This helps to promote independence among unit tests. Nearly all unit tests, i.e. performing a contextual query , require some kind of insertion logic to occur