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

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

Redis: What's Coming in the Next Releases

Salvatore Sanfilippo details the features planned for Redis’ near/mid-term future:

  • Lua scripting support (Redis 2.6)
  • High resolution expires (Redis 2.6)
  • Performances improvements when reading/writing big objects (Redis 2.6)
  • Redis cluster (Redis 3.0) > Redis Cluster is a distributed implementation of a subset of Redis standalone. Not all commands will be supported, especially we don’t support things like multi-key operations. In general we are just implementing the subset of Redis that we are sure can be made working in a solid way in a cluster setup, with predictable behaviors. >
    > Redis cluster will stress consistency in favor of ability to resist to netsplits and failures in general.
  • Replication improvements (Redis 3.0 or post 3.0)
  • Persistence improvements (post Redis 3.0)

The post also mentions a very useful gem:

Redis with both AOF and RDB enabled is very durable already, and this is the setup we suggest

Original title and link: Redis: What’s Coming in the Next Releases (NoSQL database©myNoSQL)

via: http://antirez.com/post/short-term-redis-plans.html


LDAP: It's a (Non-Relational) Database, Stupid

The topic of LDAP shows up from time to time when speaking about non-relational databases. While I do encourage you to read the whole post, just check this summary:

LDAP is a protocol and a data model for providing access to a hierarchal (tree-shaped) database. The database itself is normally referred to as a “directory” (hence the name), a bit of nomenclature inherited from its predecessor, X.500, populated with objects that are bundles of attributes. LDAP supports direct lookup of an object by name, searches through subtrees or through the whole directory for objects matching a sophisticated pattern language, atomic updates to part of or all of individual objects, and network federation.

How many of these features are fundamental parts of the what we call today NoSQL databases?

But LDAP, like the other hierarchical storage implementing the Java Content Repository spec[1], didn’t fly too high. What NoSQL can learn from LDAP history discusses some possible causes of LDAP’s “failure”.


  1. Disclaimer: years ago I’ve been a big proponent of the JCR and one of the most interesting systems I’ve built is using a JCR implementation (but also a relational database and soon another NoSQL database).  

Original title and link: LDAP: It’s a (Non-Relational) Database, Stupid (NoSQL database©myNoSQL)

via: http://codex.grimoire.ca/2011/11/25/ldap-101-its-a-database-stupid/


IT's Next Hot Job: Hadoop Guru

Larry Feinsmith (JPMorgan Chase managing director, office of the CIO) during his keynote at Hadoop World:

We’re hiring, and we’re paying 10% more than the other guys. […] There are lots of SQL skills, SAS skills, and SPSS skills, but there are not a lot of [Hadoop] MapReduce skills

Even if you don’t land at JPMorgan, it’s time to learn yourself some Hadoop.

Original title and link: IT’s Next Hot Job: Hadoop Guru (NoSQL database©myNoSQL)

via: http://www.informationweek.com/news/software/info_management/231902645?printer_friendly=this-page


Hadoop-Enabled SOA Architectures

John Akred (data and platforms lead at Accenture Technology Labs) for ZDNet:

We take the data infrastructure layer, and take data stores like Hadoop, and the existing enterprise systems that give that data valuable context and integrate those at the data layer. And we abstract that integrated data platform from the consuming applications via service-oriented data access patterns. So we’re exposing our enterprise data platform to the enterprise via services rather than direct query access.

Service oriented architectures aren’t new. But realizing the abstraction of the applications from the data layers via service oriented architectures has not been easy, and in many cases enterprises end up essentially implementing point to point interfaces over service oriented architectures. When you get to the data platform view, its really important to build well-known web services that enable data access, so that application developers are no longer having to understand the performance characteristics and implementation of a database.

This sounds more like data-centric architecture or if you want Data(base)-as-a-Service. Hadoop can be indeed an important part of a Data(base)-as-a-Platform solution on its analytic side.

Original title and link: Hadoop-Enable SOA Architecture (NoSQL database©myNoSQL)

via: http://www.zdnet.com/blog/service-oriented/service-oriented-architectures-role-in-the-emerging-hadoop-world/7880


The Big Data Boom Is the Innovation Story of Our Time

A must read article in The Atlantic by Erik Brynjolfsson and Andrew McAfee explaining what the fuzz is with Big Data or differently put why Big Data is the future:

Breakthroughs in innovation often rely on breakthroughs in measurement.

[…]

Today businesses can measure their activities and customer relationships with unprecedented precision. As a result, they are awash with data.

[…]

Science has been dominated by the experimental approach for nearly 400 years. Running controlled experiments is the gold standard for sorting out cause and effect. But experimentation has been difficult for businesses throughout history because of cost, speed and convenience.

[…]

Greg Linden, who led one set of experiments at Amazon, describes the emerging experimentation philosophy succinctly: “To find high impact experiments, you need to try a lot of things. Genius is born from a thousand failures. In each failed test, you learn something that helps you find something that will work. Constant, continuous, ubiquitous experimentation is the most important thing.”

Original title and link: The Big Data Boom Is the Innovation Story of Our Time (NoSQL database©myNoSQL)

via: http://www.theatlantic.com/business/archive/2011/11/the-big-data-boom-is-the-innovation-story-of-our-time/248215/


NoSQL Databases and Big Data Market: A Quick Look at Technology vs Funding Status

What are your first thoughts if you overlay the following graphics:

Hype Cycle for Cloud Computing 2011

Original title and link: NoSQL Databases and Big Data Market: A Quick Look at Technology vs Funding Status (NoSQL database©myNoSQL)


Accel $100m Fund for Big Data, Hadoop, and NoSQL Databases

Promising times for companies in the data space:

With its new $100 million Big Data Fund, the VC firm’s offices across the globe will invest in applications that help form an ecosystem around existing big data building blocks such as Hadoop and NoSQL. […] Rather, he’s looking for companies that add to Hadoop, NoSQL, solid-state drives or other building blocks by tuning them to become easily consumable analytics engines or by creating products to help users better visualize what their data looks like. Taking it a step further, Li is also interested in applications that might not play up their big data roots at all because the underlying technologies are just a means to an end.

Original title and link: Accel $100m Fund for Big Data, Hadoop, and NoSQL Databases (NoSQL database©myNoSQL)

via: http://gigaom.com/cloud/accel-forms-100m-fund-to-feed-big-data-apps/


Enterprises Will Have Three Classes of Databases

Dwight Merriman (CEO and founder 10gen) interviewed by InternetNews.com:

Basically every large enterprise in the world has those two buckets for sure—a relational database used for OLTP and some form of data warehouse and a business reporting and intelligence database—and what we’re seeing are enterprises adding a third bucket, which is a NoSQL database. So on a forward basis, enterprises will have three classes of databases instead of two.

The challenge for NoSQL database producers is to convince people that maintaining 3 types of databases would deliver better value to the business. The challenge for system architects is to figure out where each of these databases fit and are providing increased value over alternatives.

Original title and link: Enterprises Will Have Three Classes of Databases (NoSQL database©myNoSQL)


Hadapt Raises $9.5m Series a Financing

Speaking of funding, Hadapt, the company founded by Daniel Abadi, announced that it has closed a $9.5 million Series A round of financing led by Norwest Venture Partners (NVP) and Bessemer Venture Partners.

I haven’t heard much of Hadapt since the initial announcement, so I hope things will change.

Original title and link: Hadapt Raises $9.5m Series a Financing (NoSQL database©myNoSQL)

via: http://www.prnewswire.com/news-releases/hadapt-secures-95mm-series-a-financing-132431973.html


Basho Raises $5mil for Improving Riak

Congratulations to the Basho guys for closing an additional $5m round of funding. According to Martin Schneider “the funds will be used to make Riak an even better product. We have some seriously awesome plans for additional features, platform capabilities, cloud tools etc.”

Riak already seems like a great product to me—there’s always place for improvements though. I’d say part of the money and a tad more effort should go into making Riak a more popular product.

Details: This is the second round raised this year after the $7.5m announced in June bringing it to a total of $12.5m. The new funding comes from an inside round. Past investors in Basho have included private equity firm Georgetown Partners and Danish systems integrator Trifork AS.

Original title and link: Basho Raises $5mil for Improving Riak (NoSQL database©myNoSQL)


What Happened to CouchDB’s Popularity?

Top answer:

A lot of this is the result of the confusion in the community, there is the CouchDB Apache project, then the CouchBase work and their own “Single Server” releases that don’t necessarily map 1:1 to the Apache versions.

Then there is the CouchBase “Couch Server” offering which, from what little I can tell, is membase + CouchDB and their CouchDB build, according to their docs, isn’t 100% 1:1 with the Apache CouchDB builds (some differences about protocol or something).

Then you have no officially maintained libraries for the different platforms which was a turn off to me the first time I cracked that egg open.

Then you have CouchBase wanting to focus Couch on the mobile-cloud story since they are the only NoSQL solution doing that , with native builds for some of the mobile platforms.

Then you have BigCouch and IrisCouch and a slew of other things I can’t figure out where they fit in.

Ultimately when you enter the eco system and start digging, it is hard to figure out exactly what “CouchDB” is, where to grab binaries for your platform from and drivers for your platform. As wavephorm pointed out, you can figure it all out with some reading and digging, but you have to persist.

It’s not like Mongo, you don’t just head to the official site, grab the official binary and install the official driver.

I’d also point out that CouchDB’s biggest feature, the must-have feature no other NoSQL repo besides RavenDB replicates, is the master-master replication. If you don’t need that, your barrier to entry with the other NoSQL solutions is much easier/straight forward.

I hope at some point the CouchDB community focuses their efforts on barriers to entries and figures out a common message for beginners they can communicate, and from there introduce the customizations for the people that need them (mobile Couch, BigCouch, etc.)

If only they would have listened to what I’ve been saying all this time.

Original title and link: What Happened to CouchDB’s Popularity? (NoSQL database©myNoSQL)


Two Important Events in the NoSQL World

I’m starting to catch up with the news after my sabatical month and it turns out things didn’t stay still during this period. While there are quite a few very important things that have happened during October, I’d like to bring up two very interesting ones that mark a possible turn in the NoSQL databases world.

  1. The first insolvency/bankruptcy in the market.

    Based on a tweet from Achim Friedland, ex-development lead CTO at sones, the German graph database sones GmbH, which raised back in February another round of funding, was declared insolvent.

    This is an unfortunate validation of my thoughts about Graph Databases market penetration. sones GmbH has never been a market leader, but they could have tried to focus on a niche segment of the graph database emerging market and while that wouldn’t necessarily transform the company in a huge success, it would have probably gave it more time to refine the product and expand.

    Update: Daniel Kirstenpfad (CTO, sones GmbH) reached out to me with some clarifications:

    1. Achim Friedland was at a point in time the development lead of sones and in that position responsible for leading the developer team. He never was CTO of sones.

    2. sones is not insolvent but rather is under preliminary bankrupty administration with the goal to arrive at a solution for continuation of product and company

  2. I’m starting to notice a shift in the (marketing) message of a couple of NoSQL companies towards Enterprise NoSQL. I’m not yet sure what enterprise NoSQL means though: targeting enterprise customers, large scale NoSQL deployments, expensive NoSQL product and services packages, etc..

    Whatever this terms means, I take it as a sign of: a) the market becoming too busy; b) growing competition for paying customers ; c) investors looking for clear validations of their investments.

    What I hope this does not mean is the start of the unhealthy, unfriendly, and dirty competition. This market segment has greatly benefitted from a friendly environment in which all contenders have been pushing their products forward while working together to popularize and bring awareness to the polyglot persistence philosophy.

Original title and link: Two Important Events in the NoSQL World (NoSQL database©myNoSQL)