Redis can be a great way to keep in-memory lists. However, what happens when you need to be able to quickly search that list and be able to expire individual items after a given amount of time? None of the redis classes allow you to do this out of the box, but it can be done. I'll show you how.
Reminder from part 1: In this tutorial we’ll build a game that interacts with the Twitter API and challenges users to match a given Tweet with its author. The game is called Following, and you can play the fully-built version of it here: http://followingapp.herokuapp.com.
Creating a node.js module and publishing it to npm is a fairly straightforward process. Haven't done it yet? Not sure what I'm talking about? Here's a quick tutorial to speed you along.
A client of ours has a Rails application that needs to consume hundreds of requests per second from a third party service, with flexibility to scale upwards to thousands of requests per second. Rails just isn't well suited to handle such a high volume of requests.
Node.js, on the other hand, is a great tool when it comes to doing a simple task very fast and in high volumes. It scales easily to boot.
Aside from consuming the request, each request needs to be processed individually, and at that volume, a queue was necessary. Resque was an easy choice.
In this article, we'll show you how to create a basic Node.js application using the Express framework and deploy it to both Heroku and Nodejitsu.
- ← Previous
- Next →