3 ms·
It's a lot easier to get behind a no than a yes. As long as NoSQL is expressed as a negative, it's a very big tent. Even DBAs and relational model types have so
by mattmcknight 17y ago
It's a lot easier to get behind a no than a yes. As long as NoSQL is expressed as a negative, it's a very big tent. Even DBAs and relational model types have some complaints about SQL.
As soon as it turns into "we're using Project Voldemort, can you figure out how to hook a reporting tool up to it tomorrow?", you find a lot less consensus.
- strlen 17y agoPart of "NoSQL" is right tool for the job. You use a data warehouse for reporting which can be Hadoop+Hive/Pig or it can be a traditional OLAP solution e.g., Oracle DWH, you use Voldemort for low-latency serving. The two are differently problems. Even with an RDBMS, you shouldn't be using the same instance for reporting as you do for OLTP: that's what ETL and data warehousing are about. I should add that HBase and Cassandra support integration with Hadoop and Hive/Pig, but all the usual warnings about the load of reporting jobs against a serving database apply-- one solution (with Cassandra) that I've heard is to place a the "reporting" machines on a different network e.g., on a different vlan in your own datacenter or in a different EC2 availability zone.