Carlos Alexandre calexandrepcjr

Mistakes to Avoid: Docker Antipatterns

Whichever route you take to implementing containers, you’ll want to steer clear of common pitfalls that can undermine the efficiency of your Docker stack.

Don’t run too many processes inside a single container

The beauty of containers—and an advantage of containers over virtual machines—is that it is easy to make multiple containers interact with one another in order to compose a complete application. There is no need to run a full application inside a single container. Instead, break your application down as much as possible into discrete services, and distribute services across multiple containers. This maximizes flexibility and reliability.

Don’t install operating systems inside Docker containers

It is possible to install a complete Linux operating system inside a container. In most cases, however, this is not necessary. If your goal is to host just a single application or part of an application in the container, you need to install only the essential

Redis Cluster Setup with Docker Swarm

Setup

./redis.sh

Test

test the redis cluster

Why Most Unit Testing is Waste

By James O Coplien from http://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf

1.1 Into Modern Times

Unit testing was a staple of the FORTRAN days, when a function was a function and was sometimes worthy of functional testing. Computers computed, and functions and procedures represented units of computation. In those days the dominant design process composed complex external functionality from smaller chunks, which in turn orchestrated yet smaller chunks, and so on down to the level of well-understood primitives. Each layer supported the layers above it. You actually stood a good chance that you could trace the functionality of the things at the bottom, called functions and procedures, to the requirements that gave rise to them out at the human interface. There was hope that a good designer could understand a given function’s business purpose. And it was possible, at least in well-structured code, to reason about the calling tree. You could mentally simulate

	WITH RECURSIVE fibonacci(recursion_level, fibonacci_number, next_number)
	AS (
	# Base Case
	SELECT 0 AS recursion_level,
	0 AS fibonacci_number,
	1 AS next_number
	UNION ALL
	# Recursion query
	SELECT recursion_level + 1 AS recursion_level,
	next_number AS fibonacci_number,

	<?php

	namespace Tests\Concerns;

	use App\Models\User;
	use Tymon\JWTAuth\Facades\JWTAuth;

	trait AttachJwtToken
	{
	/**

	<?php declare(strict_types=1);

	if ($argc !== 3) {
	die("Usage: php optimise.php input.jpeg output.jpeg" . PHP_EOL);
	}

	$infile = $argv[1];
	$outfile = $argv[2];

	$img = imageCreateFromJPEG($infile);

	// 1. Even or odd

	function isEven(value){
	if (value % 2 == 0){
	return true;
	}
	else
	return false;
	}

	! model
	pc101 Generic 101-key PC
	pc102 Generic 102-key (Intl) PC
	pc104 Generic 104-key PC
	pc105 Generic 105-key (Intl) PC
	dell101 Dell 101-key PC
	latitude Dell Latitude series laptop
	dellm65 Dell Precision M65
	everex Everex STEPnote
	flexpro Keytronic FlexPro

	##########################################
	# To run:
	# curl -sSL https://gist.githubusercontent.com/andrewelkins/1adc587feb610f586f8f40b50b7efc3a/install-docker-on-linux-mint-18.sh \| bash -x
	##########################################

	# Kernel version http://stackoverflow.com/a/4024263
	versionlte() {
	[ "$1" = "`echo -e "$1\n$2" \| sort -V \| head -n1`" ]
	}
	versionlt() {

	#!/bin/sh
	#
	# libinput by default will disable the touchpad while a key is pressed.
	# to disable this, run `xinput` to list the inputs. find the name of your
	# touchpad (mine is 'Microsoft Surface Keyboard Touchpad').
	#
	# Disable the setting 'Disable While Typing Enabled'
	# `xinput --set-prop 'Microsoft Surface Keyboard Touchpad' \
	# 'libinput Disable While Typing Enabled' 0`
	#