Cyrill Schumacher SchumacherFM

How to set up stress-free SSL on an OS X development machine

One of the best ways to reduce complexity (read: stress) in web development is to minimize the differences between your development and production environments. After being frustrated by attempts to unify the approach to SSL on my local machine and in production, I searched for a workflow that would make the protocol invisible to me between all environments.

Most workflows make the following compromises:

Use HTTPS in production but HTTP locally. This is annoying because it makes the environments inconsistent, and the protocol choices leak up into the stack. For example, your web application needs to understand the underlying protocol when using the secure flag for cookies. If you don't get this right, your HTTP development server won't be able to read the cookies it writes, or worse, your HTTPS production server could pass sensitive cookies over an insecure connection.
Use production SSL certificates locally. This is annoying

Magento Enterprise 1.12 cluster

Scaling Magento presentation with 60 slides and notes, which was then reviewed by Alan Storm.

Magento Scaling Hypotheses

Magento’s checkout throughput can increase to at least 8 times its current capacity and up to 26 times more in ideal conditions.

The current checkouts per hour limit for large, real-world Magento stores is 4,500
This limit cannot effectively be increased with more and/or better hardware
The improper type handling in Magento’s SQL code is the cause of the current limit
If one SQL query is fixed, large Magento stores can scale to a new, real-world limit of 120,000 checkouts per hour
For commodity hardware, this new limit might be 36,000 checkouts per hour

Channels Are Not Enough

... or Why Pipelining Is Not That Easy

Golang Concurrency Patterns for brave and smart.

By @kachayev

Intro

Interfaces

Let's imagine a very simple table

CREATE TABLE people {
  id bigserial,
  name character varying
}

	// Just before switching jobs:
	// Add one of these.
	// Preferably into the same commit where you do a large merge.
	//
	// This started as a tweet with a joke of "C++ pro-tip: #define private public",
	// and then it quickly escalated into more and more evil suggestions.
	// I've tried to capture interesting suggestions here.
	//
	// Contributors: @r2d2rigo, @joeldevahl, @msinilo, @_Humus_,
	// @YuriyODonnell, @rygorous, @cmuratori, @mike_acton, @grumpygiant,

	delimiter ;;
	drop procedure if exists build_catalog;;
	create procedure build_catalog(IN categories INT, IN products INT)
	begin
	SET @category_count = 1;
	SET @CATNAMEPREFIX = "Category ";
	SET @CATURLKEYPREFIX = "cat-";
	SET @CATURLPATHPREFIX = "catpath-";
	SET @ROOTCATEGORY = 2;
	SET @INCLUDEINMENU = 1;

	package main

	import (
	"crypto/tls"
	"crypto/x509"
	"log"
	"net/rpc"
	)

	func main() {

	- What do Etcd, Consul, and Zookeeper do?
	- Service Registration:
	- Host, port number, and sometimes authentication credentials, protocols, versions
	numbers, and/or environment details.
	- Service Discovery:
	- Ability for client application to query the central registry to learn of service location.
	- Consistent and durable general-purpose K/V store across distributed system.
	- Some solutions support this better than others.
	- Based on Paxos or some derivative (i.e. Raft) algorithm to quickly converge to a consistent state.
	- Centralized locking can be based on this K/V store.