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

Logscape: All content tagged as Logscape in NoSQL databases and polyglot persistence

Sportingbet Decides Against Hadoop to Analyse 60Tb of Data

Andrew Coates (enterprise integration architect at Sportingbet) for ComputerWorld about the solution used, Logscape, for analysing server logs:

“The way it works is that you have a Logscape server running on dedicated hardware. Then you have a little agent running on every single machine you want to monitor, which means when you run a query, it runs the query on every single machine that you have told it to run it on,” he said.

Possible more accurate titles: “Sportingbet decides it doesn’t need all Hadoop features for log processing” or “Using Logscape at Sportingbet for in-place log processing”.

Original title and link: Sportingbet Decides Against Hadoop to Analyse 60Tb of Data (NoSQL database©myNoSQL)

via: http://www.pcadvisor.co.uk/news/network-wifi/3421452/sportingbet-decides-against-hadoop-analyse-60tb-of-data/