vasanthk

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?

kharrison

// Swift Standard Librray - String
// Keith Harrison http://useyourloaf.com

// Import Foundation if you want to bridge to NSString
import Foundation

// ====
// Initializing a String
// ====

viklas

##Instructions for setting up sirius from the Emerging Stack dockerfile (end-to-end) ####NOTE: Everything here works on a laptop, but it will run out of disk space in all likelihood, requiring an annoying boot2docker hack. It's easier and faster in the cloud. You can copy/paste each of the commands below...without the dollar or hash symbol. Remember, if you terminate your DigitalOcean droplet, you'll have to do all these steps again (but they will survive a server reboot).

####At the end of this process, you will be able to ask Sirius some wikipedia type questions (when, which, where, etc) inside a terminal window...don't expect a fancy user experience, this is raw functionality only.

###Cloud Server Provisioning Stage

1. Sign in to digitalocean and set up an account, billing, etc

2. Setup new droplet ($40 month size with Ubuntu 14.04)...wait 1 minute

jbardin

package proxy

import (
	"io"
	"log"
	"net"
)

func Proxy(srvConn, cliConn *net.TCPConn) {
	// channels to wait on the close event for each connection

acolyer

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

• http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

• Does the design expect failures to happen regularly and handle them gracefully?
• Have we kept things as simple as possible?

deckarep

/*
  A Goroutine safe pattern using channels that abstracts away the channels

  This is a concept of creating a goroutine safe object that uses channels under the covers to communicate
  with the internal map[string]string structure.  I know that typically this kind of solution may done
  with mutexes but the excercise was in using channels on purpose although they are heavier.

  Note a couple of points:

  - When using channels, you can still build a public-facing api that nicely abstracts them away, therefore

cuppster

#!/usr/bin/env python
# -*- coding: utf-8 -*-
"""
SYNOPSIS

    flask_gridfs_images.py --start
    flask_gridfs_images.py --add <IMAGE_URL>
    
DESCRIPTION

dergachev

OS X Screencast to animated GIF

This gist shows how to create a GIF screencast using only free OS X tools: QuickTime, ffmpeg, and gifsicle.

Instructions

To capture the video (filesize: 19MB), using the free "QuickTime Player" application:

woodb

#!/bin/bash
#
# Shell script to automatically configure a new Flask, nginx and uWSGI based blog 
# on an Amazon EC2 instance.
#
# See http://bit.ly/MeGwjD for more information!
#
# If you are forking this for your own custom configuration script, see the following other gists:
#   https://gist.github.com/3071737
#   https://gist.github.com/3071739

qur2

#!/bin/bash
#
# DESCRIPTION:
#
#   Set the bash prompt according to:
#    * the active virtualenv
#    * the branch/status of the current git repository (handles detached head state)
#    * the return value of the previous command
#    * the fact you just came from Windows and are used to having newlines in
#      your prompts.