Sascha pid

Overview

We run multiple server processes in two data centers. Each process listens on two ports, one for HTTP and one for HTTPS. HTTPS is terminated by Apache prior to reaching node.js. HTTP goes directly from the client to node.js (through a master load balancer). We do not use clusters. We slice our physical servers into thin virtual machines running SmartOS, each with about 3GB of memory designed for a single node.js process.

Our node.js servers are hapi.js servers using the composer functionality and plugins architecture. We have three sets of plugins loaded: mobile web front end experience (single page app), legacy API reverse proxy, and monitoring.

We also serve original node.js services off another server zone which runs closed source plugins using hapi.

Analytics

Moving from jQuery

Events

// jQuery
$(document).ready(function() {
  // code
})

The browser field is provided by a module author as a hint to javascript bundlers or component tools when preparing modules for client side use.

terms

Below are common terms used in the rest of the document

server

This is a non-dom based javascript execution environment. It usually only contains the base javascript language spec libraries and objects along with modules to communicate with OS features (available through commonjs require).

client

REST Ideology & Rants

I am getting frustrated by the number of people calling any HTTP-based interface a REST API. Today’s example is the SocialSite REST API. That is RPC. It screams RPC. There is so much coupling on display that it should be given an X rating.

REST APIs must be hypertext-driven

Roy Fielding writes a PhD dissertation describing the architectural style of the World Wide Web. He coins the term ‘Representational State Transfer’ (REST) to describe it – after all, if you’re going to talk about something, you need to give it a name. Somehow, in a semantic shift of epic fail proportions, the term REST has also come to mean something completely different to most people, a ‘style’ of writing web services. This style has no agreed protocol.

REST

External Links

General Information
Richardson Maturity Model by Martin Fowler

	// jshint devel: true
	// make a copy of each `console` methods and adds them
	// to the global object so that you can call `log('foobar')`
	// instead of the verbose `console.log('foobar')`
	// DO NOT USE IT IN PRODUCTION MODE
	// @623HS

	(function(global) {
	'use strict';
	var name, value;

	var gulp = require('gulp');
	var gutil = require('gulp-util');
	var express = require('express');
	var path = require('path');
	var tinylr = require('tiny-lr');

	var createServers = function(port, lrport) {
	var lr = tinylr();
	lr.listen(lrport, function() {
	gutil.log('LR Listening on', lrport);

	{
	"name": "my-app",
	"version": "0.0.0",
	"dependencies": {
	"browserify": "~2.36.1",
	"less": "~1.5.1"
	},
	"devDependencies": {
	"watchify": "~0.4.1",
	"catw": "~0.2.0"

	/**
	* Google-style progress indicator
	*/

	@keyframes progress {
	50% { border-width: .5em 0; }
	to { border-width: .5em 0 0 0; }
	}

	@keyframes rotate {