Oleg Lebedev olebedev

Tools for building microservices architecture (May 7, 2016)

We are obviously in the age of Microservices, Mobile first, Polyglot, post-Java JVM languages, GitHub and Docker uprise. In this world, Open Source usage dominates, and the speed of change is intense. Knowing the direction of DevOps tools and picking the right one for the project is crucial.

Terms

Continuous Integration is the practice of running your tests on a non-developer machine automatically everytime someone pushes new code into the source repository.

This has the tremendous advantage of always knowing if all tests work and getting fast feedback. The fast feedback is important so you always know right after you broke the build (introduced changes that made either the compile/build cycle or the tests fail) what you did that failed and how to revert it.

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

Deploy your own PaaS!

Setting up Dokku with DigitalOcean and Namecheap

..or how I made my own heroku in a few hours for $3.98.

This write-up owes a great deal to dscape's Node.js Deployments with Docker, Dokku, & Digital Ocean, the dokku project itself, and the fine folks working on dokku's issues. I took dscape's article as a starting point when trying this out but found some details lacking so I documented my own process for getting dokku up and running.

1. Get a domain

How to cross compile Go with CGO programs for a different OS/Arch

It is possible to compile Go programs for a different OS, even though go build says otherwise.

You'll need:

a valid toolchain for the platform/os you're targetting
Go Tip (works on 1.1 and 1.2rc1 but you might as well be on tip)
golang-crosscompile helper script https://github.com/davecheney/golang-crosscompile
the patch provided

	deploy:
	steps:
	- add-to-known_hosts:
	hostname: $HOSTNAME
	- add-ssh-key:
	keyname: KEY
	- script:
	name: Push to dokku
	code: \|
	git remote add dokku dokku@$HOSTNAME:$APP

	// takes arguments and produces an array of functions that accept context
	function handle_args() {
	var args = Array.prototype.slice.call(arguments);
	return args.map(function(arg) {
	if(arg instanceof Function) return arg; // Presumably already a contex-accepting function.
	if(arg instanceof Array) return and.apply(this, arg); // make arrays behave as and.
	// Presuming a string, build a function to check.
	var my_regex = new RegExp(arg.toString(), 'i');
	return function(context) {
	return context.search(my_regex) > -1;

	box: wercker/golang
	# Add services here
	# Build definition
	build:
	# The steps that will be executed on build
	steps:
	# Sets the go workspace and places you package
	# at the right place in the workspace tree
	- setup-go-workspace

	function Promise() {
	var callbacks = [],
	promise = {
	resolve: resolve,
	reject: reject,
	then: then,
	safe: {
	then: function safeThen(resolve, reject) {
	promise.then(resolve, reject);
	}

	#!/bin/sh

	# OPTIONAL FLAGS:
	#
	# -geoip true
	# this will install maxmind geoip and auto update crontab file
	#
	# -cloudwatch true
	# this will install aws cloud watch metrics and send them to aws dashboard
	#

	package main

	import (
	"fmt"
	"log"
	"net"
	"net/mail"
	"net/smtp"
	"crypto/tls"
	)