The personal program I am working on is starting to have a lot of different objects, by design. So I started thinking about a way to store the entire object into a database, as opposed to using Derby and adding the properties, elements links to other objects all into seperate fields. If I was to take the final database and design it in 3rd normal form it would be a massive amount of tables with the need for more complicated SQL statements. Ultimately increasing overhead. It was suggested that I use a NoSQL database like MongoDB. The problem with Mongo as I see it is not embeddable, which means it will need to be installed onto the user machine independently (or during the install procedure). Please correct me if I am wrong, I know nothing of NoSQL DB's. Also, I would need to either make sure Mongo is running when I run the application or start and stop it with the application.
I want to avoid that, I have seen several NoSQL databases listed that CAN be embedded in a
Java application. Can anyone suggest some, and some resources I can read up on this? I was just getting comfortable with Derby when I realized a NoSQL option would be better.
Thanks
If I release a program to the world, I'll have to include the coderanch as well as some select people in the credits. This place and the people are awesome. I can't wait to get to a point I'm more the helper than helpee