There are no pure NoSQL or pure SQL projects/solutions, sooner or later you will end up using both SQL and NoSQL, with NoSQL it can be even worse. I have seen project that are using 2 and more different NoSQL solutions. For example, mongodb for documents and neo4j as a graph database and some other database for relational data. Hybrid approach simplifies all this, you just have to plan and choose wisely.
There are number of solutions on the market that support best from both worlds. Oracle and postgres both have support for NoSQL datatypes. Informix went even further, it gives you ability to mix classic relational tables with NoSQL collection in the same database. You can write a query that will access data from both table and collection at the same time. You can use compression, timeseries it also supports mongodb API so you can write application that will connect to Informix using mongodb drivers, and of course you can shard as much as you want with no pain. Just google hybrid sql.
Slashdot Mirror
There are no pure NoSQL or pure SQL projects/solutions, sooner or later you will end up using both SQL and NoSQL, with NoSQL it can be even worse. I have seen project that are using 2 and more different NoSQL solutions. For example, mongodb for documents and neo4j as a graph database and some other database for relational data. Hybrid approach simplifies all this, you just have to plan and choose wisely.
There are number of solutions on the market that support best from both worlds. Oracle and postgres both have support for NoSQL datatypes. Informix went even further, it gives you ability to mix classic relational tables with NoSQL collection in the same database. You can write a query that will access data from both table and collection at the same time. You can use compression, timeseries it also supports mongodb API so you can write application that will connect to Informix using mongodb drivers, and of course you can shard as much as you want with no pain. Just google hybrid sql.