I don’t think that database does what you think it does.
1-Minute (or Less) Summary
Lots of people look for excuses to use a technology in favor other another technology. Sometimes it is because they really like the “new” technology. Sometimes it is because they really dislike the “old” technology. Me! I prefer to use the right technology! So when you need to provide
- Document-based data
- Key-Value pairs
- Wide column stores
You really need to consider Oracle NoSQL.
The Whole Story
Honestly, I am a relational database guy. I’ve endured unstructured or poorly structured databases where people simply wanted to avoid using a relational database, Oracle or any other RDBMS. Selecting a technical option as a means to avoid a better solution is not the right answer.
Writing that! I have to be equally honest that I sometimes have tried to force my relational database expertise onto solutions that don’t always map appropriately to relational database models.
Here are two glorious things. One, Oracle NoSQL gives you all the advantages of using a solution that is flexible, high-volume, and built for big data without the complexities of fitting this in the ACID constraints of an Oracle database. Two, it gives you these advantages with storage in a database instead of a file system, simple structures instead of no structures, high volume reads and writes instead of just writes, and real-time instead of batch oriented processing. (NOTE: I am comparing to both HDFS and MongoDB).
Now, this is just my perspective. Don’t take my word for it. I’m a relational database guy more than anything else. Learn from the experts in this technology, and the absolutely wonderful resources that one on my fellow UA experts has curated just for you.
The Oracle NoSQL UA Resource page is here to both get you started, and take you deeper into the world of the Oracle NoSQL database.
