such as SimpleDB, BigTable, Cassandra, CouchDB, and MongoDB .
I recommend a few excellent podcasts on Cassandra , CouchDB and MongoDB to get a sense of what this is all about.
Recently, MongoDB has received a lot of attention due to the following factors:
availability on many platforms
rich language support: C, C++, C#, Java, Javascript, Perl, PHP, Python, Ruby
binary json for efficient storage
equivalent of …
- The "Tech. Arch.": Implementing Ruby Camping REST Services With RESTstop
- The "Tech. Arch.": Transform Your Ruby Camping Web App Into An OAuth Provider
- New Relic: Ruby developers: Get visbility into Resque, Authlogic, Paperclip and Camping with New Relic's rpm_contrib gem
- SD Ruby Podcast: Episode 002: Camping
- Ruby Best Practices: Name that method: Symmetry
- EdgeCase - Home: From Camping to Sinatra + DataMapper + Mustache (part 1)
…Major Types of Column-Stores by Daniel Abadi. I have noticed that Bigtable, HBase, Hypertable, and Cassandra are being called column-stores with increasing frequency, due to their ability to store and access column families separately. This makes them appear to be in the same category as column-stores such as Sybase IQ, C-Store, Vertica, VectorWise, MonetDB, ParAccel, and Infobright, which also are able to access columns separately.
Cloud Economics, By The …
- igvita.com: Future of RDBMS is RAM Clouds & SSD
- Engine Yard Ruby on Rails Blog: LDAP Directories: The Forgotten NoSQL
- James on Software: Most NoSQL DBs Are Not Scalable
- paperplanes: NoSQL And You - Thoughts On Finding Right Partner In Chrime
- Viget Extend : The Development Lab: NoSQL Misconceptions
- Blue Box Group: News: NoSQL Meetup at Blue Box Group - New Confirmed Date
…Google and Amazon's broad use of their non-relational BigTable and Dynamo systems. We evaluated all the usual open source NoSQL suspects. After considerable debate, we decided to go with Cassandra.
We don't deserve anything. Publishers can do whatever they want. If you don't like it, don't send them nasty emails or browse their sites with ad-blockers: just don't support them. Don't read their content, don't link to them, and …
- MicroISV on a Shoestring: Dashboard Design For Metrics-savvy Software Companies
- A Fresh Cup: Double Shot #657
- Rails Inside: Remail: Send and Receive E-mail Through Google App Engine for Free
- Katz Got Your Tongue?: The Blind Men and the Elephant: A Story of Noobs
- blog.mhartl | Michael Hartl's tech blog: Some rvm gotchas
- RubyLearning Blog: Showcasing RubyLearning's Awesome Rubyists
…engineer Stu Hood, who explained Cassandra's appeal: "Over the Bigtable clones, Cassandra has huge high-availability advantages, and no single point of failure. When compared to the Dynamo adherents, Cassandra has the advantage of a more advanced datamodel, allowing for a single row to contain billions of column/value pairs: enough to fill a machine. You also get efficient range queries for the top level key, and even within your values."
- Spyced: And now for something completely different
- Spyced: Cassandra: Fact vs fiction
- Mike Perham: Cassandra Internals - Writing
- Viget Extend : The Development Lab: Database Taxonomy
- High Scalability: Hot Scalability Links for March 19, 2010
- Axon Flux // A Ruby on Rails Blog: WTF is a SuperColumn? An Intro to the Cassandra Data Model (Arin Sarkissian explains)
Record stores: BigTable, HBase, HyperTable, and Cassandra.
Scalable RDBMSs: MySQL Cluster, ScaleDB, Drizzle, and VoltDB.
The paper describes each system and then compares them on the dimensions of Concurrency Control, Data Storage Replication, Transaction Model, General Comments, Maturity, K-hits, License Language.
And the winner is: there are no winners. Yet. Rick concludes by pointing to a great convergence:
I believe that a few of these systems will …
…you've got a bunch of other data models in the middle: graph databases, tabular databases like BigTable, and document databases like Mongo.
There are a few different ways that you can think about document databases. One of the nice things about document databases is that they're closely mapped to how most developers are writing code, whereas SQL databases were designed for accounting and banking 30 or 40 years ago, prior to the advent of web applications and the rise of object-oriented …
- Locomotivation: TweetSaver.com Launched on MongoDB, MongoMapper
That seems to be one of the big paradigm shifts for developers. When they start using something like BigTable where the data is distributed across a lot of nodes, they have to think a little differently about the way they build applications.
Working our way from the bottom up, talk a little bit about thinking differently in how you store your data so that you can use a MapReduce process on top of that.
Amr: First, it's worth making the important clarifying point that Hadoop is not …
- High Scalability: Hot Scalability Links for Nov 24 2009
- Heroku: Our travels continue
- Aloha On Rails - Hawaii Ruby on Rails Conference - Waikiki - Oct 5-6 2009: Thinking in Map Reduce Video Now Online
- Rails Envy » Home: Rails Envy Podcast - Episode #093
- igvita.com: Easy Map-Reduce With Hadoop Streaming
BigTable
On one end of the spectrum is Scalaris which is entirely memory-driven, and Redis which is primarily memory oriented (you can do background snapshots). Cassandra, BigTable, Hypertable, Hbase allow configuring how large the Memtable can get, so that provides a lot of control. The document stores - CouchDb, MongoDb and Riak - all seem to be using on-disk B+ trees, and Voldemort…
- paperplanes: NoSQL And You - Thoughts On Finding Right Partner In Chrime
- a work on process: Weekend Links
- a work on process: Friday Links - January 8th 2010
- Viget Extend : The Development Lab: Coming Soon: The NoSQL Series
- RailsTips by John Nunemaker: Getting A Grip on GridFS
- DigitalHobbit: Building a Twitter Filter With Sinatra, Redis, and TweetStream
…mapping layer for distributed column-oriented data stores (inspired by Google's BigTable) such as HBase and Cassandra. Adapted from ActiveRecord, BigRecord is designed to work as a drop-in for Rails applications.
Wen-Tien Chang's slideshare presentation Rails Best Practices from kungfurails.
Alchemist is a fine Ruby unit conversion library designed for readability and convenience.
Limelight GUI Framework …
…GAE offers a lot of great benefits, such as free load-balancing and access to the BigTable datastore amongst many other things, but it does so by abstracting or removing some of the interfaces we're all used to: there is no filesystem, BigTable is not a relational database, cron jobs are HTTP calls, and so on. While an inconvenience at first, the functionality is still there but it does require some extra work on behalf of the developer. For example, while ActiveRecord does not work …
- Think in code - Home: Rails template for Google app engine
- Videos related to 'Ruby on Rails VS Django - Commercial #7 of 9': Google I/O 2008 - Python, Django, and App Engine
- Andrzej on Software: Google App Engine and dynamic languages