mhink

Webapps as microservices

About a year ago, we migrated the Hailo back end platform to a microservice architecture. At the same time, we tried to imagine what our webapps could look like if they followed the same principles:

Small, independently developed tools
Easily replaceable and upgradeable
Organised around business capabilities
Continuous delivery and automated deployment
In applying this to front end code, we had some worries: that the user experience of flipping between multiple webapps will be jarring; and that maybe we would waste time duplicating code between webapps.

mhink

  jbarrow: can repro in console
  mkniel: The 500 errors?
  jbarrow: m? nah, scope to field thing
  jbarrow: locking up
  mkniel: oh, cool
  jbarrow: there's a certain input size for which that scopes.subsets.flatMap(scopesToOptionalProfileFields.get).toSet.flatten just hangs
  wblack: yeah it's really odd
  wblack: just go with lists
  jbarrow: m? no, I want subsets
  snewton: Streams

mhink

/**
 * Module dependencies.
 */

var express = require('express')
  , routes = require('./routes')

var app = module.exports = express.createServer();

mhink

export WORKING_DIR=~/work/textaurant
cd $WORKING_DIR; mvim; gitx

tmux start-server
tmux new-session -d -s Textaurant -n work

tmux new-window -tTextaurant:1 -n server
tmux new-window -tTextaurant:2 -n test

tmux send-keys -tTextaurant:0 'cd $WORKING_DIR' C-m