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

Typical Big Data Architecture

A bit of an old post by Venu Anuganti putting in the same diagram different components involved in a Big Data architecture.

Any data architecture loosely consists of four major logical components:

Typical Big Data Architecture

I don’t think there’s a blueprint for big data architectures. But such a diagram can give you a could idea of the possible components involved. Then to make things simple for engineers, you start adding requirements, constraints, and SLAs at each level. Once you have some sort of idea of how things will look, you start building it and discover that some of the components you are planning to use don’t work well together or there’s no way to achieve those SLAs. All in all, it’s a fun job.

Original title and link: Typical Big Data Architecture (NoSQL database©myNoSQL)

via: http://venublog.com/2012/11/30/typical-big-data-architecture/