A few links to stuff I was jabbering on about this eve (doing no them no justice most likely) in case anyone cares..
Design for Continuous Experimentation
tldr; Don't write off Build-Meaure-Learn
Event Sourcing Pattern
tdlr; Get yer state back...
CQRS In Railstldr; Split yer architecture in to reads and writes, eventual constancy of your denomalized read models is yer mate when ye need to scale.
The talk doesn't seem to be online anywhere anymore but this is a copy of the pdf I attached to my post about it a while back.
CQRS + Event Sourcing in Rails (some code)
Some code from the same dude who did the talk "CQRS Diet" above which shows CQRS in Rails with Event Sourcing... :
VIDEO: One Queue (kinda) to Rule Them All
tldr; Micro-services that do one thing well and delegate questions out of process...
Great talk -> Fred George - Implementing Micro-Service Architecture
CODE: (Reactive) React,js
tdlr; bitta code I hacked on to learn React.js and leverage RxJS
This was an experiment which I have ran with since, to see if I can achieve the rendering perf (does 60fps with 100 cells) with React virtual dom.
Basically when you add any data to the observable source, this is pushed through (by invoking observers).
The dude that wrote RxJS scolded me on twitter and told me to swap in the rxjs lite version, haven't been assed yet. Just don't just the JS size.
Some Other Rx Jazz
The Rx stuff, is really funky, checkout some of the talks from ReactConf