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



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

A Different Approach to Data Modeling: Thinking of Data Service Requirements

Pedro Visintin:

We can distinguish several objects: Session, Cart, Item, User, Order, Product and Payment. Usually we use ActiveRecord to store all of them. But this time let’s think about it differently.

For sessions, we don’t need durable data at all — Redis can be a good option, and of course will be faster than any RDBMS. For Cart and Item,we will need high availability across different locations. Riak can fit well for this use case. For User Order Product and Payment, a relational database can fit well, focusing on Transactions and Reporting about our application.

This is a very good exercise for understanding the requirements for your data service layer. As much as I write about polyglot persistence, when architecting an application never leave aside or ignore the operational requirements for your service.

Original title and link: A Different Approach to Data Modeling: Thinking of Data Service Requirements (NoSQL database©myNoSQL)


What Is Unique About LinkedIn’s Databus

After learning about LinkedIn’s Databus low latency data transfer system, I’ve had a short chat with Sid Anand focused on understanding what makes Databus unique.

As I’ve mentioned in my post about Databus, Databus looks at first as a data-oriented ESB. But what is innovative about Databus comes from decoupling the data source from the consumers/clients thus being able to offer speed to a large number of subscribers that are up-to-date, but also help clients that fall behind or are just bootstrapping without adding load on the source database.

Databus clients are smart enough to:

  1. ask for Consolidated Deltas since time T if they fall behind
  2. ask for a Consistent Snapshot and then for a Consolidated Delta if they bootstrap

and Databus is build so it can serve both Consolidate Deltas and Consistent Snapshots without any impact on the original data source.

Databus Boostrapping

Diagram from

The “catching-up” and boostrapping processes are described in much more details in Sid Anand’s article.

Databus is the single and only way that data is replicated from LinkedIn’s databases to search indexes, the graph, Memcached, Voldemort, etc.

Original title and link: What Is Unique About LinkedIn’s Databus (NoSQL database©myNoSQL)

The Future is Polyglot Persistence

Marting Fowler and Pramod Sadalage in an infographic promoting their upcoming book (PDF):

Polyglot persistence will occur over the enterprise as different applications use different data storage technologies. It will also occur within a single application as different parts of an application’s data store have different access characteristics.

There are over 2 years since I’ve begun evangelizing polyglot persistence. By now, most thought leaders agree it is the future. Next on my agenda is having the top relational vendors sign off too. Actually, I’m almost there: Oracle is promoting an Oracle NoSQL Database and Microsoft is offering both relational and non-relational solutions with Azure. They just need to say it.

Original title and link: The Future is Polyglot Persistence (NoSQL database©myNoSQL)

How Polyglot Persistence and Having Data Storage Options Changes Things

No 2012 predictions. Just facts.

GigaOm’s Barb Darrow commenting on Oracle’s Q2 financial results:

This is bad news for the company which pinned its cloud hopes on specialized data center appliances — the Exadata database machine, Exalogic middleware/application appliance, Exalytics analytics engine as well as a proposed ”Big Data Appliance.” This is the third consecutive quarter where Oracle posted hardware sales declines but this is probably more painful because the company is finally now fully engaged in its big data center appliance push.

An anonymous commenter:

As a low to mid range customer, I was disenfranchised by oracle, and we have gotten rid of segments of oracle in our data center. Just recently they have shown interest in us again so perhaps the low margin equipment will be back. Sun was not focused enough, and Oracle was too focused. Hopefully they are finding an profitable and useful middle ground.

Kent Langley:

So, NoSQL database #9999 there are many other equally usable solutions that are far more transparent in the way they do business and foster community around their products.  This isn’t about paying money.  This is about trust.  So, sorry NoSQL #9999, but I’ll not be entering your sales cycle in this fashion or evaluating your product at this time.  Moving along now…

Original title and link: How Polyglot Persistence and Having Data Storage Options Changes Things (NoSQL database©myNoSQL)

Polyglot Platform

Even if Heroku’s post is about polyglot programming and commodifying deployments, many of the points apply to polylgot persistence. Especially this one:

The result of all this diversity is that the safe bet, especially for large organizations, is to standardize on a single language and avoid (or even outright forbid) development in any others. Polyglot programming allows using the right tool for the job, offering substantial gains in speed and agility of development; but the switching cost of changing out the entire stack of deployment, scaling, management, and monitoring infrastructure necessary for an app written in a different language creates an intractable obstacle to reaping the benefits of polyglot.

Original title and link: Polyglot Platform (NoSQL database©myNoSQL)


NoSQL/NewSQL/MySQL Is Not a Zero Sum Game

Although there will be isolated examples, it is going to be rare, therefore, that any potential adopter would be directly comparing NoSQL and NewSQL technologies unless they are still at the stage trying to figure out the level of consistency required for an individual application.

I believe that the future will bring these technologies together so being aware of their pros and cons will be essential. Categorizing all of storage and processing engines just from the level of consistency perspective is like saying there’s only transactional data out there. We all know that’s not true at all.

Original title and link: NoSQL/NewSQL/MySQL Is Not a Zero Sum Game (NoSQL database©myNoSQL)


SQL Access to CouchDB Views

Nicholas Goodman:

[…] enabling SQL Access to CouchDB Views […] single, biggest advantage is: The ability to connect, run of the mill, commodity BI tools to your big data system.

While the video below doesn’t show a PRPT it does show Pentaho doing Ad Hoc, drag and drop reporting on top of CouchDB with LucidDB in the middle, providing the connectivity and FULL SQL access to CouchDB. Once again, the overview:

CouchDB LucidDB pentaho

Being able to bring together both structured and unstructured data—it doesn’t really matter if it is BigData or not—, query it with a language that is familiar to many developers and that had tons of tools available represents the future of polyglot persistence.

Original title and link: SQL Access to CouchDB Views : Easy Reporting | Goodman on BI (NoSQL database©myNoSQL)


Basho, NoSQL, and Polyglot Persistence Adoption With Justin Sheehy

Justin Sheehy (CTO Basho) answers Michael Coté’s (RedMonk) questions about Basho, the current state of NoSQL, and polyglot persistence adoptions among developers.


Poll: What Database Does Your Company Use?

Just a Hacker News poll, nothing scientific though. MySQL has twice the votes of PostgreSQL which is in the second place.

Original title and link: Poll: What Database Does Your Company Use? (NoSQL database©myNoSQL)

NoSQL and Polyglot Persistence Adoption

Tim Berglund’s apt comments about NoSQL technology:

I think the basic lesson NoSQL is forcing us to learn is that we actually have to think about the way we store and retrieve data—that there isn’t just one data model or query idiom or scaling paradigm to rule them all. We now have a healthy set of options available to us whose different characteristics will be more suitable or less suitable to different applications. This makes it hard (and probably wrongheaded) to pick a favorite.

Polyglot persistence adoption:

I think it’s technologically possible, but it’s clearly not a cultural reality yet. I talk to more developers who say, “I don’t really know what NoSQL is all about” than I do developers who are trying to make decisions about how to store their data. This will probably change on the same five- to ten-year time frame that it will take us to learn how not to use the various NoSQL products.

And the common pitfalls:

The most obvious are the resume-driven motivations we all have to select NoSQL databases right now. It’s a technology in its hype phase, so everybody wants on the bandwagon so they can talk about their Real Production Experience with a particular product. This is going to cause project failures over the next couple of years, just like it does with every other hyped technology before we discover how to use them properly.

Original title and link: NoSQL and Polyglot Persistence Adoption (NoSQL databases © myNoSQL)


Polyglot Persistence: The Architecture of the Future

The architecture of the future based on polyglot persistence:

Polyglot persistence

From Brad Anderson’s Introduction to NoSQL presentation:

Original title and link: Polyglot Persistence: The Architecture of the Future (NoSQL databases © myNoSQL)

Polyglot Persistence

Emil Eifrem [1]:

We’re big believers in whole concept of polyglot persistence and polyglot persistence is the observation that in the future and even today datasets are just so complex that in order to get both convenience in programming, but also runtime benefits such as performance and scalability, you need to take parts of your dataset and squeeze them into different types of databases.

[1] Emil Eifrem: CEO NeoTechnologies, @emileifrem

Original title and link: Polyglot Persistence (NoSQL databases © myNoSQL)