Browse files

more readme

  • Loading branch information...
1 parent c923962 commit 165c6e18d18d788a449211684d2f53e979cda31f @JustinBeckwith committed Jan 29, 2013
Showing with 6 additions and 6 deletions.
  1. +6 −6
@@ -1,18 +1,20 @@
+ [1]:
+ [2]: (View the Demo)
[Wazstagram]( is a fun experiment with node.js on [Windows Azure]( and the [Instagram Realtime API]( The project uses various services in Windows Azure to create a scalable window into Instagram traffic across multiple cities.
## How does it work
The application is written in node.js, using cloud services in Windows Azure. A scalable set of backend nodes receive messages from the Instagram Realtime API. Those messages are sent to the front end nodes using [Windows Azure Service Bus]( The front end nodes are running node.js with [express]( and [](
![WAZSTAGRAM Architecture]( "WAZSTAGRAM Architecture")
-## Websites, Virtual Machines, and Cloud Services, oh my.
+## Websites, and Virtual Machines, and Cloud Services, Oh My!
One of the first things you need to grok when using Windows Azure is the different options you have for your runtimes. Windows Azure supports three distinct models, which can be mixed and matched depending on what you're trying to accomplish:
@@ -47,7 +49,7 @@ The [azure npm module]( provides the basis for a
`npm install azure`
+After you have the azure module, you're ready to rock.
## The Backend
@@ -196,8 +198,6 @@ The [frontend](
## Learning
The whole point of writing this code for me was to explore building performant apps that used a rate limited API for data. Hopefully this model can effectively be used to accept data from any API responsibly, and scale it out to a number of connected clients to a single service. If you have any ideas on how to make this app better, please let me know, or submit a PR!

0 comments on commit 165c6e1

Please sign in to comment.