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
Thursday, 18 November 2010
‹ Back

MongoDB: Dealing with Schema(less) Databases

About:
,

What I get with Mongo is a pretty organic type of database. I can add stuff as i need it without worrying about writing DML/DDL and managing that. […] Because it is such and unstructured system, I’ve built structure into it by creating an API which the application layer talks to. The rule is that if you need to talk to the DB, you talk via the API, not directly.

How would you deal with schema free data sources in multi-applications single database environments?

Original title and link: MongoDB: Dealing with Schema(less) Databases (NoSQL databases © myNoSQL)

via: http://blog.securekidsnet.com/post/1613062182/technology