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)

via: http://news.dice.com/2012/04/06/nosql-and-sql/

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)

via: http://blog.heroku.com/archives/2011/8/3/polyglot_platform/

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)

via: http://blogs.the451group.com/information_management/2011/07/11/nosql-newsql-mysql-not-a-zero-sum-game/

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:

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)

via: http://www.nicholasgoodman.com/bt/blog/2011/06/22/sql-access-to-couchdb-views-easy-reporting/

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

via: http://www.redmonk.com/cote/2011/06/20/justin-sheehy-on-basho-nosql/

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)

via: http://groovy.dzone.com/news/dzone-interviews-tim-berglund

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)

via: http://www.infoq.com/interviews/eifrem-graphdbs