A Look at the NoSQL Landscape
This article is part of the DZone NoSQL Resource Portal, which is brought to you in collaboration with Neo Technology and DataStax. Visit the NoSQL Resource Portal for additional tutorials, videos, opinions, and other resources on this topic.
Take a look at the current landscape of NoSQL stores and figure out why you might need NoSQL in this recent podcast where Bruce Elgort talks with Mark Myers from the London Developer Co-op. Here's a shortlist of the things they will discuss:
- How NoSQL became so popular
- Breakdown of the types of NoSQL databases - (Key-Value, Column, Document, Graph)
- Explanation for why you might need NoSQL
- IBM's history with NoSQL functionality in Lotus Notes NSF
- Review of CouchDB, MongoDB and other open source NoSQL stores
- Javascripts unique roll in NoSQL
- Discussion about IBM XWork Server and XPages
Download the Podcast (Ep. 142 ~40min)
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)
Neo Technology and DataStax are leading the charge for the NoSQL movement. You can learn more about the Neo4j Graph Database in the project discussion forums and try out the new Spring Data Neo4j, which enables POJO-based development. You can also see how Apache Cassandra, a ColumnFamily data store, is pushing the boundaries of persistence with cloud capabilities and deployments at SocialFlow and Netflix.





Comments
Aniceto Garcia replied on Thu, 2012/01/26 - 4:37am
NoSQL databases typically use clusters of cheap commodity servers to manage the exploding data and transaction volumes, while RDBMS tends to rely on expensive proprietary servers and storage systems. The result is that the cost per gigabyte or transaction/second for NoSQL can be many times less than the cost for RDBMS, allowing you to store and process more data at a much lower price point.
Java Collection