Eric Redmond @coderoshi NoSQL databases are fun, and we've all wired up a Node.js project to use one. But what about two? What about three?

That's what's on the docket for this talk. We'll do all the things:

• Walk through a (very) quick intro on CouchDB, Neo4j, and Redis.
• Then learn how to interact with these very different databases using Node.js.
• Then wire them up into a single web application (using Bricks.js, for good measure)
• Write it all in CoffeeScript… buzzword overload!!!

If you do not walk out of this talk excited and maybe a little confused, I will have failed.

Jerry Sievert @jerrysievert Bricks.js is fast modular framework built on node.js. This session will be a mix of an introduction for those who have not used it, and building a fairly simple application using it.

Jesse Hallett @hallettj JavaScript is a language that is tremendously flexible, but that comes with few clear conventions. Code organization is one are that has been reinvented perhaps more times than there are JavaScript programmers. I will examine a few tools that are intended to improve the experience of writing object-oriented code.

Some of the specific tools that I plan to examine are traits.js, CoffeeScript, Prototype, and JiverScripts. The goal is to get a look at different ideas to see what each approach has to offer. We will discuss inheritance versus composition, and question when it is or is not appropriate to use object-oriented code.

Audience participation is encouraged: if you have a favorite OO implementation, or experiences with JavaScript code organization, feel free to come and to share.

Ward Cunningham @WardCunningham Our new wiki innovates three ways. It shares through federation, composes by refactoring and wraps data with visualization.

The Smallest Federated Wiki project wants to be small in the "easy to learn powerful ideas" version of small. It wants to be a wiki so that strangers can meet and create works of value together. And it wants to be federated so that the burden of maintaining long-lasting content is shared among those who care.

Subbu Allamaraju @sallamar Node.js is a great platform for building I/O bound apps. At eBay, my team applied node.js to solve a very common chore - how to get data from server-side HTTP APIs (or "web services") quickly. ql.io is a result of this work.

ql.io consists of two parts:

• A SQL + JSON inspired DSL for HTTP
• A runtime that you can can either deploy as an HTTP gateway or use as a JS API for node.js based apps.

In this talk, I will show how you can use ql.io, the agility and performance gains that ql.io can bring in, and then take a deep dive into some of the design choices we made under the hood.

Scott Koon @lazycoder Everyone talks about Node.js in terms of non-blocking I/O and creating a web service or web site using JavaScript. But there is more to Node.js than just Sockets, ports, and protocols. I'll explore some of the non-web exclusive uses of Node.js. Node can be a code compiler, an FTP server, a continuous integration server, a mail server, a deployment server, or an IRC server. Node can provide system reports, build and package your projects, and parse ePub books.

Kyle Drake @kyledrake There are very powerful things you can do with Node.JS, particularly with projects needing a lot of I/O operations. At Geoloqi, we have used Node.JS and Socket.IO to build a JavaScript client that allows our developers to map real-time tracking on a browser with almost no code needed. Our first project using this is MapAttack!, a truly real-time location-based geofencing game.

https://geoloqi.com/blog/tag/node-js/

Ken Robertson @krobertson Years ago I always enjoyed the BattleBots show on TV and loved teams' ingenuity and inspiration to essentially build something only to have it gloriously destroyed. But is there a way we can bring that to the software world? What if we could leverage the cloud to orchestrate scalable battles.

Garann Means @garannm There's plenty of cool stuff Node offers purely in terms of server-side architectures, but it also offers a way to solve a problem we've been wrestling with since client-side applications became a big deal: writing everything twice. Rather than having the templates that produce markup exist in one backend language and in JavaScript, you can reuse them. Instead of validating in JavaScript on the client for the user's convenience and then again in some other language on the server for security, you can share a validation module that can be used in both scenarios. And so on. We'll look at some of the ways to stop repeating ourselves in Node apps and focus on getting the most out of existing client-side code.

Aaron @Aaronontheweb Microsoft is moving towards making Windows Azure a PaaS cloud capable of hosting applications of any shape, size, framework, and programming language, and Node.JS is one of the first non-.NET technologies we've made a first-class citizen on Windows Azure.

Daniel Erickson @TechWraith Many frameworks have been created to allow you to build apps on Node.js - Express, Matador, and Flatiron to name a few. But none of these frameworks are built with development velocity, backwards compatibility, and speed. This is where Geddy steps in. Geddy is a framework built and battle tested by the JS team at Yammer. It's currently running our upload service. During this talk I'll walk you through building a basic web app with geddy, and show you how we used it to build a prototype mobile site for Yammer in less than 12 hours.

Kav Latiolais @kavla If you're not using node to build collaborative real time applications you might as well be using rails. In this talk we'll discuss patterns and pitfalls of synchronous node apps. We'll roll up our sleeves and dig into some code demonstrating patterns that can help you get started building highly interactive applications that sync real time state with Node.js, Socket.io, and Backbone.js. You will leave this talk with insight on how to build synchronous experiences into your applications and avoid some of the pitfalls we've suffered.