davidfowl

$/
  artifacts/
  build/
  docs/
  lib/
  packages/
  samples/
  src/
 tests/

MrBretticus

Notes based on Greg Young's business perspective presentation

http://skillsmatter.com/podcast/agile-testing/greg-young-cqrs-event-sourcing-the-business-perspective 

With a standard structural model we make assumptions of what the business may or may not want in the future. How can we presume to know what to track and what to discard.

CQRS/ES benefits:
* Captures behaviour explicitly, events carry the intent of users.
* We can derive any possible model about data that may be required.
* Allows domain experts and users to look at today in any way they may want to.

fwielstra

/* The API controller
   Exports 3 methods:
   * post - Creates a new thread
   * list - Returns a list of threads
   * show - Displays a thread and its posts
*/


var Thread = require('../models/thread.js');
var Post = require('../models/post.js');

jeffrafter

var express = require('express');
var sys = require('sys');
var oauth = require('oauth');

var app = express.createServer();

var _twitterConsumerKey = "YOURTWITTERCONSUMERKEY";
var _twitterConsumerSecret = "YOURTWITTERCONSUMERSECRET";

function consumer() {