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

Bloomberg says Cloudera raises at least $200m in new round

Dina Bass and Serena Saitto (Bloomberg):

Cloudera Inc. is raising at least $200 million in a new round of financing from investors including Intel Corp., according to people with knowledge of the situation.

Not confirmed yet.

Original title and link: Bloomberg says Cloudera raises at least $200m in new round (NoSQL database©myNoSQL)

via: http://www.bloomberg.com/news/2014-03-18/cloudera-said-to-raise-at-least-200-million-in-funding.html


A simple distributed algorithm for small idempotent information

In this blog post I’m going to describe a very simple distributed algorithm that is useful in different programming scenarios. The algorithm is useful when you need to take some kind of information synchronized among a number of processes. The information can be everything as long as it is composed of a small number of bytes, and as long as it is idempotent, that is, the current value of the information does not depend on the previous value, and we can just replace an old value, with the new one.

While reading this post from Salvatore Sanfilippo all I was visualizing were the diagrams in James Micken’s “The saddest moment” paper.

Original title and link: A simple distributed algorithm for small idempotent information (NoSQL database©myNoSQL)

via: http://antirez.com/news/71


2014 State Of Database Tech: Think Retro

Joe Masters Emison for InformationWeek:

Today’s database landscape isn’t just static. It’s positively retro. Remember 2004? Facebook had just launched, the iPad wasn’t even a twinkle in Steve Jobs’ eye, and Gartner’s database market share report put IBM (34.1%), Oracle (33.7%), and Microsoft (20%) in the top spots. In our survey, Microsoft, Oracle, and IBM still hold the top spots; we do add MySQL, but that’s about it for innovation. […]

And those relational databases from Microsoft, Oracle, and IBM? They’re essentially just updated versions of the companies’ 2004 offerings.

You’ll see these numbers in many surveys. But there are a couple of things to keep in mind while reading them:

  1. the enterprise world is well-known to be a late adopter. A very late adopter actually.
  2. many of these databases are subscription based so customers are locked-in on at least an yearly basis
  3. many of these databases have been acquired together with hardware and consultancy/support. Another type of lock-in.
  4. none of these databases is showing the growth in demand, jobs, and revenue that the top NoSQL databases are seeing for the last 12-18 months.

When you already bought a house, it’s quite difficult to go out looking for a new one. But there’s no good reason for you not to look and get the best appliances and furniture for your house.

Original title and link: 2014 State Of Database Tech: Think Retro (NoSQL database©myNoSQL)


April 3 Webinar: The BlueKai Playbook for Scaling to 10 Trillion Transactions a Month [sponsor]

myNoSQL’s supporter Aerospike is getting ready for a new case study webinar:


As the industry’s largest online data exchange, BlueKai knows a thing or two about pushing the limits of scale. Find out how they are processing up to 10 trillion transactions per month from Vice President of Data Delivery, Ted Wallace.

Register today.

Original title and link: April 3 Webinar: The BlueKai Playbook for Scaling to 10 Trillion Transactions a Month [sponsor] (NoSQL database©myNoSQL)


NoSQL vendor Basho restaffs barren executive ranks

Joab Jackson (Computerworld) quoting the newly appointed CEO of Basho, Adam Wray:

The previous leadership was intelligent and brought a lot of skills to the table, but have not run companies of this size and with this meteoric growth.

[…]

Quite frankly, some people were just getting tired, and needed a change in venue.

Many founders and engineers talk about their companies and products as their babies. And there’s a very difficult decision to make to step away for the benefit of your babies when realizing that there may be better ways to raise them.

Maybe that’s the case with what’s happening at Basho.

Original title and link: NoSQL vendor Basho restaffs barren executive ranks (NoSQL database©myNoSQL)

via: http://www.computerworld.com/s/article/9246945/NoSQL_vendor_Basho_restaffs_barren_executive_ranks


End of an era at Basho

Jack Clark for The Register:

The Register has learned that CTO Justin Sheehy will soon be off to pastures unknown; chief architect Andy Gross today revealed he is leaving to take up a position at Twitter; and CEO Greg Collins left in January.

This marks the end of an era at Basho. Only the future, if there’s one, will tell if this was a good or bad era.

Original title and link: End of an era at Basho (NoSQL database©myNoSQL)

via: http://www.theregister.co.uk/2014/03/10/basho_changes/


A Couchbase stack for under $1000

In this article we are going to look at how you can build an awesome cloud based solution with a lot of headroom and power for Couchbase for under $1000!

Getting 8 servers (2 reverse proxies, 2 app servers, 4 database nodes) for this money sounds like a sweet deal.

Original title and link: A Couchbase stack for under $1000 (NoSQL database©myNoSQL)

via: http://scalabilitysolved.com/build-a-kick-ass-couchbase-stack-for-under-1000/


Topology: The Architecture of Distributed Systems [sponsor]

Words from the special myNoSQL sponsor, Couchbase:


You can’t judge a book by its cover, but you can judge the architecture of a distributed system by its topology.

If two distributed systems are equally effective, is the one with the simpler topology the one with the better architecture? This article compares the architecture of two document databases and two wide column stores by looking at their topologies.

Document Databases

Topology #1

doc_db_one

Wow. There is a lot going on here. There are four node types and two layers of logical groupings.

Topology #2

doc_db_two

Nice. Simple. There is one node type.

Which document database would you choose?

  • Which one is going to be easier to deploy?
  • Which one is going to be easier to maintain?
  • Which one is going to be easier to scale?
  • Which one is going to be more resilient?

I believe the less moving parts, the better.

Read more on system topologies.

Original title and link: Topology: The Architecture of Distributed Systems [sponsor] (NoSQL database©myNoSQL)


Snapdeal selects Aerospike to improve shopper satisfaction over MongoDB, Couchbase and Redis [sponsor]

Words from the long time myNoSQL supporter, Aerospike, reporting on a success story of a customer deploying Aerospike to deal with massive demand growth:


After experiencing 500% growth in 2013, Snapdeal, India’s largest online marketplace, switched from 10 MongoDB servers to just two Linux servers on Amazon EC2 with Aerospike, and reduced response times to less than a millisecond.

Read the case study to learn more.

Original title and link: Snapdeal selects Aerospike to improve shopper satisfaction over MongoDB, Couchbase and Redis [sponsor] (NoSQL database©myNoSQL)


Integrating D3 with CouchDB

A 4-part series by Mike Bostock describing various integrations paths of D3 and CouchDB:

  1. Part 1: saving a D3 app in CouchDB
  2. Part 2: storing D3 library in CouchDB and storing data in CouchDB
  3. Part 3: accessing CouchDB data from D3
  4. Part 4: data import

Original title and link: Integrating D3 with CouchDB (NoSQL database©myNoSQL)


The NoSQL KISS [sponsor]

In the words of the special sponsor, Couchbase:


Kelly knew it. The U.S. Navy knows it. You know it.

Keep it Simple, Stupid (KISS)

The Problem

We categorized NoSQL implementations. The categories include distributed caches, key / value stores, and document databases. However, what if application requirements span multiple categories? Do you add Redis, Riak, and MongoDB? The result would not be simple, stupid.

whatthehellhaveyoubuilt

The Solution

Let distributed caching, key / value storage, and document handling be use cases. The solution is a single NoSQL implementation that supports multiple use cases. In fact, Viber recently solved this problem. Their previous architecture relied on MongoDB for document processing and Redis for distributed caching. Their current architecture relies on Couchbase Server as a single replacement for both MongoDB and Redis. Read the full story.

Original title and link: The NoSQL KISS [sponsor] (NoSQL database©myNoSQL)


Big doubts on big data: Why I won't be sharing my medical data with anyone

Jo Best (ZDNet) talking about the privacy concerns of having centralized, non-regulated, non-anonymised healthcare data:

If ever there was an open goal for big data, healthcare should be it.

By gathering information from doctors, patients, drug companies, insurers, and charities, and putting the big data machinery to work on analysing it, we should be able to get better insights into a range of conditions and then come up with better ways to treat them.

I’m happy I’m not the only one concerned about all these.

Original title and link: Big doubts on big data: Why I won’t be sharing my medical data with anyone (NoSQL database©myNoSQL)

via: http://www.zdnet.com/uk/big-doubts-on-big-data-why-i-wont-be-sharing-my-medical-data-with-anyone-yet-7000026497/