Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We use Redis (Moodstocks) #6

Closed
catwell opened this issue Dec 21, 2010 · 3 comments
Closed

We use Redis (Moodstocks) #6

catwell opened this issue Dec 21, 2010 · 3 comments

Comments

@catwell
Copy link

catwell commented Dec 21, 2010

I have followed the "let us know" link at http://www.redis.io/topics/whos-using-redis. I just wanted to tell you that we use Redis (through Ohm) as our main datastore in our applications Moodstocks Notes and Moodstocks Contacts, and to store some data (mainly statistics and credentials) in Moodstocks API.

References:
http://www.moodstocks.com/discover-our-products/
http://www.moodstocks.com/2010/11/26/the-tech-behind-moodstocks-notes/
http://www.moodstocks.com/2010/12/20/the-tech-behind-moodstocks-api/
http://mashable.com/2010/12/18/moodstocks/
http://techcrunch.com/2010/12/10/moodstocks-notes-is-stickybits-without-the-barcodes/

Feel free to add us to the users page if you like :)

@catwell
Copy link
Author

catwell commented Dec 21, 2010

Oh, and BTW you could also add Ohm in the list of available clients for Ruby: http://ohm.keyvalue.org/ It is a high-level O(R)M (think ActiveRecord, but lighter) that relies on Nest https://github.com/soveran/nest, which itself uses redis-rb.

@djanowski
Copy link
Contributor

3366673 is this fine?

Also, Ohm is not a client really, but we definitely need to migrate the old page that listed mappers.

@catwell
Copy link
Author

catwell commented Dec 22, 2010

Yes, that's fine, thanks.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants