ofan

Backend Architectures

Twitter

ror, scala, jetty, erlang, thrift, mongrel, comet server, my-sql, memchached, varnish, kestrel(mq), starling, gizzard, cassandra, hadoop, vertica, munin, nagios, awstats

Introduce Gizzard of Twitter - 트위터의 새로운 분산 관리 라이브러리 Gizzard를 소개합니다.
The Architecture Twitter Uses to Deal with 150M Active Users, 300K QPS, a 22 MB/S Firehose, and Send Tweets in Under 5 Seconds
Scaling Twitter: Making Twitter 10000 Percent Faster

How to setup your own CA with OpenSSL

For educational reasons I've decided to create my own CA. Here is what I learned.

First things first

Lets get some context first.

Suppose we want to add support for a new iOS 8 API in our framework that replaces an older iOS 7 API. There are a few problems we might face:

The new API will crash if we call it on iOS 7
The new API won't compile if we build it using the iOS 7 SDK
The old API will raise a deprecation warning if built with a deployment target of iOS 8 and up

These three problems require three different technical solutions:

We can avoid calling the new API on an old OS version by using runtime detection (e.g. respondsToSelector:)
We can avoid compiling new APIs on old SDKs using the __IPHONE_OS_VERSION_MAX_ALLOWED macro

Experimental Docker Libnetwork DHCP Driver

The DHCP driver is intended for users to be able to integrate Docker IP address management with their existing IPAM strategies that use DHCP for dynamic address assignment. DHCP enables users to allocate addresses in an organized fashion that will prevent overlapping IP address assignment by associating a unique MAC address from the container eth0 Ethernet interface to an IP address as determined by the DHCP pools defined in the DHCP configuration.

This driver only provides the DHCP client functionality. It does not include a DHCP server. The default driver offers single-host IPAM or for distributed multi-host orchestrated IPAM see the libnetwork overlay driver.

Getting Started

Download the driver compiled into Docker Engine - docker binary with libnetwork test dhcp client spam driver

Microsoft Windows and Office KMS Setup

At the beginning of 2030, I found this essay in my archives. From what I know today, I think it was very insightful at the moment of writing. And I feel it should be published because it can teach us, Rust developers, how to prevent that sad story from happening again.

What killed Haskell, could kill Rust, too

What killed Haskell, could kill Rust, too. Why would I even mention Haskell in this context? Well, Haskell and Rust are deeply related. Not because Rust is Haskell without HKTs. (Some of you know what that means, and the rest of you will wonder for a very long time). Much of the style of Rust is similar in many ways to the style of Haskell. In some sense Rust is a reincarnation of Haskell, with a little bit of C-ish like syntax, a very small amount.

Is Haskell dead?

	BAD_RES_STATE \| 0x25B161 \| destroy_ctx - context doesn't exist or doesn't match type
	BAD_RES_STATE \| 0x4A6FC9 \| destroy_ctx - context in use
	BAD_RES_STATE \| 0x60DA55 \| destroy_dct - dct not in drained state
	BAD_PARAM \| 0x67A6F2 \| slrg doesnt support write;
	BAD_PARAM \| 0x0F0E35 \| ppamp doesnt support write;
	BAD_PKT \| 0x4A22F \| access reg MAD with specified register id not supported
	BAD_PKT \| 0x16C592 \| mad_ifc: process_smp_lid mkey check failed - silently discarded
	INTERNAL_ERR \| 0x079233 \| set_get_port_info: silently discarded.
	BAD_PKT \| 0x468496 \| mad_ifc: ATTRV_SM_INFO handled by SW
	BAD_PKT \| 0x071808 \| mad_ifc: smp trap repress silently discarded after processing.