Michael Richards mikeric

The introduction to Reactive Programming you've been missing

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

A new Rails API project

This super lightweight Rails API project will contain the following bits of awesomeness to get you started on your new app.

Rails API (https://github.com/rails-api/rails-api)
Sass (http://sass-lang.com)
Coffeescript (http://coffeescript.org)
Postgres (http://www.postgresql.org)
Rivets.js (http://rivetsjs.com)
Bootstrap (http://getbootstrap.com)

Building a Maintainable, Agile Architecture for Realtime, Transactional Apps

A maintainable application architecture requires that the UI only contain the rendering logic and execute queries and mutations against the underlying data model on the server. A maintainable architecture must not contain any logic for composing "app state" on the client as that would necessarily embed business logic in the client. App state should be persisted to the database and the client projection of it should be composed in the mid tier, and refreshed as mutations occur on the server (and after network interruption) for a highly interactive, realtime UX.

With GraphQL we are able to define an easy-to-change application-level data schema on the server that captures the types and relationships in our data, and wiring it to data sources via resolvers that leverage our db's own query language (or data-oriented, uniform service APIs) to resolve client-specified "queries" and "mutations" against the schema.

We use GraphQL to dyn

	/* vim:set ts=2 sw=2 sts=2 expandtab */
	/*jshint asi: true undef: true es5: true node: true devel: true
	forin: false latedef: false */
	/global define: true /


	if (typeof(WeakMap) === 'undefined') WeakMap = (function(global) {
	"use strict";

	function defineNamespace(object, namespace) {