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
Friday, 28 January 2011
‹ Back

Jarvis Architecture Using MongoDB for Asset Information

About:
,
,
,
,

Jarvis architecture[1] powered by NoSQL:

Jarvis Architecture MongoDB

We chose a hybrid approach for data. We store user and organization data in MySQL but asset information is in MongoDB. This lets us have a traditional schema for organizations having many users and users that have many organizations. We chose a document database for our asset information because the “schema” we had in mind would be a hot mess in a relational database. The freedom of a Mongo enables some really great features which we’ll be unveiling over time.

  1. Jarvis: open source Perl-based web asset management system  ↩

Original title and link: Jarvis Architecture Using MongoDB for Asset Information (NoSQL databases © myNoSQL)

via: http://www.coldhardcode.com/blog/2011/01/jarvis-technical-notes.html