Virendra Singh Bhalothia bhalothia

System Design Cheatsheet

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

Basic Steps

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?

People

`:bowtie:`	😄 `:smile:`	😆 `:laughing:`
😊 `:blush:`	😃 `:smiley:`	☺️ `:relaxed:`
😏 `:smirk:`	😍 `:heart_eyes:`	😘 `:kissing_heart:`
😚 `:kissing_closed_eyes:`	😳 `:flushed:`	😌 `:relieved:`
😆 `:satisfied:`	😁 `:grin:`	😉 `:wink:`
😜 `:stuck_out_tongue_winking_eye:`	😝 `:stuck_out_tongue_closed_eyes:`	😀 `:grinning:`
😗 `:kissing:`	😙 `:kissing_smiling_eyes:`	😛 `:stuck_out_tongue:`

This gist contains everything you need to install StatsD and Graphite on CentOS 6.3. Unless I forgot something. If I did, shoot a reminder email to noah at one more bug dot com. tl;dr: womm, ymmv, yolo.

I (mostly) followed the steps shown in the EZUnix wiki

And I also referred back to this gist by Michael Grace

	# Automated AMI and Snapshot Deletion
	#
	# @author Bobby Kozora
	#
	# This script will search for all instances having a tag named "Backup" with a value of "Backup".
	# As soon as we have the instances list, we loop through each instance
	# and reference the AMIs of that instance. We check that the latest daily backup
	# succeeded then we store every image that's reached its DeleteOn tag's date for
	# deletion. We then loop through the AMIs, deregister them and remove all the
	# snapshots associated with that AMI.

	# Automated AMI Backups
	#
	# @author Bobby Kozora
	#
	# This script will search for all instances having a tag with the name "backup"
	# and value "Backup" on it. As soon as we have the instances list, we loop
	# through each instance
	# and create an AMI of it. Also, it will look for a "Retention" tag key which
	# will be used as a retention policy number in days. If there is no tag with
	# that name, it will use a 7 days default value for each AMI.

	#!/usr/bin/env python3
	import json

	import boto3

	def main():
	all_ec2 = {}
	all_rds = {}
	all_cache = {}
	all_elb = {}

	import boto3
	import logging

	#setup simple logging for INFO
	logger = logging.getLogger()
	logger.setLevel(logging.INFO)

	#define the connection
	ec2 = boto3.resource('ec2')

	from collections import defaultdict

	import boto3

	"""
	A tool for retrieving basic information from the running EC2 instances.
	"""

	# Connect to EC2
	ec2 = boto3.resource('ec2')

	$> brew cask install java

	$> brew install kafka

	$> vim ~/bin/kafka
	# ~/bin/kafka
	#!/bin/bash

	zkServer start
	kafka-server-start.sh /usr/local/etc/kafka/server.properties

	CREATE TABLE t_random AS SELECT s, md5(random()::text) FROM generate_Series(1,5) s;
	INSERT INTO t_random VALUES (generate_series(1,1000000000), md5(random()::text));

	SELECT pg_size_pretty(pg_relation_size('t_random'));