Glenn Nagel gnagel

Understanding Comparative Benchmarks

I'm going to do something that I don't normally do, which is to say I'm going to talk about comparative benchmarks. In general, I try to confine performance discussion to absolute metrics as much as possible, or comparisons to other well-defined neutral reference points. This is precisely why Cats Effect's readme mentions a comparison to a fixed thread pool, rather doing comparisons with other asynchronous runtimes like Akka or ZIO. Comparisons in general devolve very quickly into emotional marketing.

But, just once, today we're going to talk about the emotional marketing. In particular, we're going to look at Cats Effect 3 and ZIO 2. Now, for context, as of this writing ZIO 2 has released their first milestone; they have not released a final 2.0 version. This implies straight off the bat that we're comparing apples to oranges a bit, since Cats Effect 3 has been out and in production for months. However, there has been a post going around which cites various compar

WARNING MAY BE INCORRECT AND INCOMPLETE, USE AT YOUR OWN RISK

Install Proxmox, RancherOS, in a VM with Rancher 2.0 and Portainer

Setup Proxmox

Install Proxmox 5.3
Console/SSH into Proxmox
nano /etc/apt/sources.list
edit the file to look like this

Note:

When this guide is more complete, the plan is to move it into Prepack documentation.
For now I put it out as a gist to gather initial feedback.

A Gentle Introduction to Prepack (Part 1)

If you're building JavaScript apps, you might already be familiar with some tools that compile JavaScript code to equivalent JavaScript code:

Babel lets you use newer JavaScript language features, and outputs equivalent code that targets older JavaScript engines.

Enable Docker Remote API with TLS client verification

Docker's Remote API can be secured via TLS and client certificate verification.
First of all you need a few certificates and keys:

CA certificate
Server certificate
Server key
Client certificate
Client key

Create certificate files

A SaltStack AWS Auto Scaling Solution

Overview

The AWS Auto Scaling Goup, configured with a customised Cloud-Init file, sends a notification to an SNS Topic, which in turn passes it onto an SQS queue that the Salt Master is subscribed to. A Reactor watches for the auto scaling events and pre-approves the new minion based on its Auto Scaling group name and instance ID.

Salt Master Configuration

Building

go build -o goencrypt main.go

	package main

	import (
	"context"
	"crypto/sha1"
	"encoding/hex"
	"fmt"
	"io"
	"os"
	"path/filepath"

	package main

	import (
	"context"
	"crypto/sha1"
	"encoding/hex"
	"fmt"
	"io"
	"os"
	"path/filepath"

	// Package gaepb is copied from cloud.google.com/go/datastore/internal/gaepb,
	// which copied a subset of google.golang.org/appengine/internal/datastore.
	// It includes the Reference, Path, and Path_Element protos.
	//
	// They are copied there, and here, to provide compatibility to decode keys
	// generated by the google.golang.org/appengine/datastore package. Copying the
	// minimal amount of protos to support key decoding means we don't need to add
	// a dependency on the appengine/datastore package.
	//
	// Other than the above comment, code generated by protoc-gen-go. DO NOT EDIT.

	[0] Pre-requisites

	Install google-cloud-sdk in your laptop
	Documentation: https://cloud.google.com/sdk

	Install helm in your laptop.
	Documentation: https://helm.sh/docs/using_helm/#installing-helm

	Get latest Istio.
	curl -L https://git.io/getLatestIstio \| ISTIO_VERSION=1.1.7 sh -