Suresh Kumar toddlers

Scaling your API with rate limiters

The following are examples of the four types rate limiters discussed in the accompanying blog post. In the examples below I've used pseudocode-like Ruby, so if you're unfamiliar with Ruby you should be able to easily translate this approach to other languages. Complete examples in Ruby are also provided later in this gist.

In most cases you'll want all these examples to be classes, but I've used simple functions here to keep the code samples brief.

Request rate limiter

This uses a basic token bucket algorithm and relies on the fact that Redis scripts execute atomically. No other operations can run between fetching the count and writing the new count.

First Method

Deleting the .git folder may cause problems in our git repository. If we want to delete all of our commits history, but keep the code in its current state, try this:

# Check out to a temporary branch:
git checkout --orphan TEMP_BRANCH

# Add all the files:
git add -A

This is free and unencumbered software released into the public domain.

Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.

In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit

Kubectl output options

Let's look at some basic kubectl output options.

Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).

We can start with:

kubectl get no

Docker Cli Tips and Tricks

My favorite command line options and best practices

Bash/zsh completion
use Tab to populate command line, narrows down options as you go, fills in container names, ID's, images, volumes. Huge time saver.

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

	"""
	This module implements an Ansible plugin that is triggered at the start of a playbook.

	The plugin dynamically generates a tag for each role. Each tag has the same name as its role.
	The advantage of this is that it saves you some boilerplate, because you don't have to wrap
	all tasks of a role in an additional block and assign a tag to that.
	Additionally, it works automatically when you add new roles to your playbook.

	Usage is exactly the same as without this plugin:

	# ssh key generator data source expects the below 3 inputs, and produces 3 outputs for use:
	# "${data.external.ssh_key_generator.result.public_key}" (contents)
	# "${data.external.ssh_key_generator.result.private_key}" (contents)
	# "${data.external.ssh_key_generator.result.private_key_file}" (path)
	data "external" "ssh_key_generator" {
	program = ["bash", "${path.root}/../ssh_key_generator.sh"]

	query = {
	customer_name = "${var.customer_name}"
	customer_group = "${var.customer_group}"

	package main

	import (
	"fmt"
	"os"
	"os/exec"
	"syscall"
	)

	func main() {

	##TCP FLAGS##

	Unskilled Attackers Pester Real Security Folks
	==============================================
	TCPDUMP FLAGS
	Unskilled = URG = (Not Displayed in Flag Field, Displayed elsewhere)
	Attackers = ACK = (Not Displayed in Flag Field, Displayed elsewhere)
	Pester = PSH = [P] (Push Data)
	Real = RST = [R] (Reset Connection)
	Security = SYN = [S] (Start Connection)