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

Muscula Architecture: Node.js, MongoDB, and CDN

Allan Ebdrup:

The frontend interfaces with the backend entirely through JSONP calls and the only thing passed through those JSONP calls is pure data as JSON strings. There is no html-markup whatsoever on the backend. The separation between frontend and backend is logical as well as physical. The frontend is hosted on entirely different servers than the backend and on a different domain. […] The backend is build with Node.JS and MongoDB. The backend is also layered in tiers. There is a layer for security, a layer for returning uniform error messages and status codes and other layers.

Among the listed advantages of such an architecture:

  • one programming language in the entire technology stack: JavaScript.
  • scalable
  • very fast load time for the users of the application
  • schemaless database
  • no ORM

And obviously this is a much better solution than having the front-end directly access the data store.

Original title and link: Muscula Architecture: Node.js, MongoDB, and CDN (NoSQL database©myNoSQL)

via: http://www.muscula.com/architecture