1. WAVO.ME
Using node.js in production

2. “Giving your multimedia a home on the web”
What is wavo.me?

3. FIXING THE DISCONNECT
Between your online content and your main methods of
storage and organization

4. ORGANIZING YOUR MEDIA
Not only aggregate, but also organize

5. WHY NODE.JS
What factors made us choose node.js over competing
technologies

6. OUR STACK
Node.js, Mongo DB, Redis, Backbone.js, Socket.io

7. "rocket" : ">= 0.1.0"
, “arachne-client” :”>=0.0.1”
, "imagemagick" : ">= 0.1.2"
, "knox" : ">= 0.0.9"
, "express-messages" : ">= 0.0.2"
, "bcrypt" : ">= 0.2.3"
, "cookies" : ">= 0.1.6"
, "keygrip" : ">= 0.1.7"
, "nodemailer" : ">= 0.1.18"
, "embedly" : ">= 0.3.4"
, "async" : ">= 0.1.9"
, "underscore" : ">= 1.1.6"
, "oauth" : ">= 0.9.2"
, "oo" : ">= 0.0.3"
, "mongoose" : ">= 1.8.3"
MODULES USED
A peak into our package.json

8. EXPRESS AND CONNECT
Why not simply use Express?

9. ROCKET.JS
Our framework which builds on Express adding functionality for
team projects

10. CONVENTION > CONFIGURATION
Some simple conventions can save lots of time as the team
grows

11. CONTROLLERS & VIEWS
Uniform connections between URL routing and templating

12. • Uniform workflow for the developer
• Focuses the developer on the current problem
• Always know where functionality belong
CONTROLLERS & VIEWS

13. CLIENT DIRECTORY
The use of require.js

14. • A desire for uniform client / server code
• Consistent templating formats
• What about optimizations ?
CLIENT DIRECTORY

15. • Require.js is available
• There exists many browser templating engines
• Tedious optimizations with separate code bases
CLIENT DIRECTORY

16. • Runtime file watching
• Compiled template files
• Environment controlled by simple flag
• Automatic resource optimizations
CLIENT DIRECTORY

17. EXPORTS & DNODE
Blurring the line between client code and server code

18. • Consistent interface with controllers
• RPC over socket.io
• Server side exports always available
EXPORTS & DNODE

19. LOCALES
Production applications require simple and easy ways to be
displayed in any language

20. SPLITTING CONCERNS
Many modules and even completely separate projects

21. 400 VS
500
MY fault YOUR fault
SIMPLE INTERFACES
Be clear about what module caused the error

22. ARACHNE
Communicating over a persistent HTTP connection

23. Load Balancer

24. WAVO.ME
Thanks for listening, be sure to check out:
rocketJS.net
&
wavo.me