nosql future: All content tagged as nosql future in NoSQL databases and polyglot persistence
What are your first thoughts if you overlay the following graphics:
Original title and link: NoSQL Databases and Big Data Market: A Quick Look at Technology vs Funding Status ( ©myNoSQL)
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 ( ©myNoSQL)
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 ( ©myNoSQL)
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? ( ©myNoSQL)
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.
The first insolvency/bankruptcy in the market.
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:
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.
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
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 ( ©myNoSQL)