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

NoSQL use case: All content tagged as NoSQL use case in NoSQL databases and polyglot persistence

Reinventing Reliable Queues With Redis Lua Scripting

Salvatore Sanfilippo:

Redis 2.6 support for Lua scripting opens a lot of possibilities, basically because you can do atomically a lot of things that before required to pay a big performance hit.

In this blog post I want to show a pattern based on the scripting capability that can be used to implement reliable queues.

I know I might upset a few people, but this feels like reinventing some wheels. Having server-side scripting support in Redis makes it a possible good fit for many new use cases, so I don’t think there’s a need to reinvent solutions that can already address an even wider range of scenarios.

Original title and link: Reinventing Reliable Queues With Redis Lua Scripting (NoSQL database©myNoSQL)

via: http://antirez.com/post/250


Real-Time Analytics With Storm and Esper

Thomas Dudziak:

At work, we recently started using Esper1 for realtime analytics, and so far we quite like Esper. It is a great tool at what it does – running queries continuously over data. The problem however then becomes how to get data into Esper. The recently released Storm2 could be one way to do that, so I got curios and started playing around with it to see if it could be made to work with Esper. And it turns out, the integration is straightforward.

Dmitriy Ryaboy


  1. Esper: complex event processing framework 

  2. Storm: distributed and fault-tolerant real-time computation: stream processing, continuous computation, distributed RPC. 

Original title and link: Real-Time Analytics With Storm and Esper (NoSQL database©myNoSQL)

via: http://tomdzk.wordpress.com/2011/09/28/storm-esper/


Jarvis Architecture Using MongoDB for Asset Information

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