I am trying to decide between a NoSQL (MongoDB) or a SQL (Oracle) database for my project. This database will be used to store output files from a set of parameters.
I can model this as a MongoDB document, so that the parameters and their values are stored as a key:value pair. Afterwards, I would query those documents in Java by sending an example HashMap.
I can also model this as a SQL table. In this situation I would create a hash index based on the parameters and their values. I would query those entries of the table in Java by rebuilding the hash and sending it within a SQL Select.
I figured that the NoSQL modeling makes more sense, since the parameters and their values would be stored on a cleaner manner. Also, querying it would make more sense on a maintenance point of view. Rebuilding a hash and making sure the hash is consistent across the board would be a maintenance overhead with SQL.
On the other hand, I have made some testing with both alternatives and the NoSQL one seems to be the slowest to return the queries (double the time of a SQL query by the has index, and it makes sense to be this way).
This seems to me like a common problem someone had before me. Still, I could not find any comparison of this type of modeling on NoSQL and SQL on an article so that I could read from someone else's perspective.
Is this a common problem on database modeling? Did I go right about testing it? Do my conclusions make sense? Is there anywhere I can find an article with a simillar problem? I have searched a lot for it and all I could find were superficial comparisons between NoSQL and SQL. Maybe I have not used proper keywords for it.