gregnwosu

#System Design Cheatsheet

Picking the right architecture = Picking the right battles + Managing trade-offs

##Basic Steps

1. Clarify and agree on the scope of the system

• User cases (description of sequences of events that, taken together, lead to a system doing something useful)
  • Who is going to use it?
  • How are they going to use it?

gregnwosu

package nl.mdj.fpinscala

import akka.actor.Actor.Receive
import akka.actor.{Props, Actor, ActorSystem, ActorRef}
import akka.pattern.ask
import akka.util.Timeout
import nl.mdj.fpinscala.KeyValueStore.ListKeys
import scala.concurrent.{Await, Future}
import scala.concurrent.duration._
import scalaz._

gregnwosu

Scala problems

(descending in severity, IMO)

ControlThrowable

Scala exposes runtime implementation details to users! See the pitfalls around catching Throwable: http://www.tzavellas.com/techblog/2010/09/20/catching-throwable-in-scala/

Increasing the visibility of private methods is not binary-compatible

https://issues.scala-lang.org/browse/SI-8899

gregnwosu

#!/bin/bash -e

bindir=`pwd`/bin-tmp
mkdir -p $bindir
export PATH=$bindir:$PATH
function use_ld() {
        rm -f $bindir/ld
        ln -s $1 $bindir/ld
        echo "Using $1 for ld"
}