ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

Spire: All content tagged as Spire in NoSQL databases and polyglot persistence

Drawn to Scale Announces Spire for Mongo

Bradford Stephens (CEO Drawn to Scale):

Today, we’re announcing that we’ve ported MongoDB onto Spire as a platform. What this means is:

  1. You can easily scale your MongoDB cluster to 200+ TB
  2. You don’t need to change a line of code in your app to make it scale
  3. You can use ANSI SQL (yes, joins), Mongo queries, and Hadoop on the same data.

Just a couple of thoughts:

  1. the push of NoSQL databases to get SQL support is growing extremely fast. But I still doubt this is happening thanks to the advantages of SQL, but more due to the 30 years of investments in the SQL ecosystem.
  2. I don’t agree with Bradford’s “MongoQL is also great because unlike SQL, there is only one flavor”. As far as I can tell, MongoDB comes with 3 flavors of queries: the object-based query language, the aggregation framework (a combination of object-based QL and pipelining) and the Javascript-based MapReduce
  3. last but not least, what are Ryan Rawson’s thoughts about Drawn to Scale going Mongo.

Original title and link: Drawn to Scale Announces Spire for Mongo (NoSQL database©myNoSQL)

via: http://drawntoscale.com/announcing-spire-for-mongo/


The NoSQL Community Threw Out the Baby With the Bath Water

Monte Zweben interviewed by Gery Menegaz for ZDNet:

“The NoSQL community threw out the baby with the bath water. They got it right with flexible schemas and distributed, auto-sharded architectures, but it was a mistake to discard SQL,”

After reading the above, I was ready to file this together with The Time for NoSQL Standards Is Now; which by the way dates from July 2012.

Then it is only the final paragraph that clarifies what Monte Zweben is talking about: a SQL engine for Hadoop. I don’t know if the order makes any difference, but before taking about thrown babies:

  1. this is not SQL for NoSQL databases
  2. there’s already Hive for SQL on Hadoop
  3. there’s already Spire from Drawn to Scale for ANSI SQL on Hadoop
  4. there’s already Hadapt for SQL and Hadoop

Original title and link: The NoSQL Community Threw Out the Baby With the Bath Water (NoSQL database©myNoSQL)

via: http://www.zdnet.com/the-nosql-community-threw-out-the-baby-with-the-bath-water-7000010361/