I used morphia for some smaller projects over a year now. Since a few weeks we're developing larger app that's dealing with really a lot more data and we quickly reached the point where morphia wasn't able to do certain things and we ended up writing code directly against the driver API. I won't go too much into detail now, since it would be a bit offtopic.... Our conclusion was that we needed the best performing json mapper we could find and it seems like the jackson-based mongo-jackson-mapper is the fastest out there!
Integrating these mappers was very easy. Switching from one to the other was also very easy. I'm curious about Igor's approach :-) Am 29.12.2011 um 15:32 schrieb angelochen: > Hi Christian, > > The two mappers you pointed out, morphia seems more Hibernate like, what's > the reason you switch to Jacson? Thanks, > > Angelo > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/T5-3-1-mongodb-tp5106689p5107779.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
