acolyer

Internet Scale Services Checklist

A checklist for designing and developing internet scale services, inspired by James Hamilton's 2007 paper "On Desgining and Deploying Internet-Scale Services."

• http://mvdirona.com/jrh/talksandpapers/jamesrh_lisa.pdf

Basic tenets

• Does the design expect failures to happen regularly and handle them gracefully?
• Have we kept things as simple as possible?

benschw

FROM ubuntu

RUN dpkg-divert --local --rename --add /sbin/initctl
RUN ln -s /bin/true /sbin/initctl

RUN echo "deb http://archive.ubuntu.com/ubuntu precise main universe" > /etc/apt/sources.list
RUN apt-get update
RUN apt-get upgrade -y

RUN apt-get -y install mysql-client mysql-server

adamwiggins

Make it real

Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discuss around concrete examples, not hand-waving abstractions. Don't say you did something, provide a URL that proves it.

Ship it

Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.

Do it with style

derekcollison

I have some early benchmark results for our work on a high performance NATS server in Go.

Quick Summary:
We can process ~2M msgs/sec through the system, and the ingress and egress are fairly well balanced.

The basics of the architecture are intelligent buffering and IO calls, fast hashing algorithms and subject distributor/routing, and a zero-allocation hand-written protocol parser.

In addition, I used quite a bit of inlining to avoid function overhead, no use of defer, and little to no object allocation within the fast path. I will share more details and the code at a future date.

ikbear

下面是陈首席陈临怀发表在微博上的 [NetScreen的往事]，我在看的过程中将其拷贝出来，整理成文，方便想看的人一口气看完。微博见：http://weibo.com/huailinchen

［NetScreen的往事］下午要在厦门见邓锋。突然又想起了许多NetScreen的往事。我是一个能写代码的文艺青年。决定在weibo上，来写写过去，算作为逐渐老去的我们的一点纪念。。。

［NetScreen的往事（1）］2001年的9月11日的早晨。我大概7点左右被人叫醒。纽约遭遇攻击！“。在电视上我看着第2架飞机冲入Tower Building，恍惚做梦一般。。。 上午去公司。。。大家都很担心。知道NetScreen的创办人Feng和Yan也在纽约，处理公司上市的事情。大家都很担心他们。我们是兄弟。

［NetScreen的往事（2）］应该是中午的时候传来消息。他们已经跑到亚特兰大去了。在等待转机。。。大家都在等着他们的回来。记得是晚上7点左右，夏天的加州，依然天很亮。我和Shalang（现Juniper Beijing Director）在楼下抽烟。看见Feng和Yan下车了。。。我是个很感情化的人，冲上去拥抱了Feng。

［NetScreen的往事（3）］Yan是个比较严肃的人，而我的工作基本上是他和Yuming［Palo Alto创办人，今年上市，发大了］直接领导。他经常修理我。有点怕他。不敢和他拥抱。Feng很随和，喜欢开玩笑［含黄色段子］。大家都喜欢他。。。

jcoglan

$VERBOSE = nil
require File.expand_path('../rooby', __FILE__)


Person = Rooby::Class.new 'Person' do
  define :initialize do |name|
    @name = name
  end
  
  define :name do

tomdale

WARNING

This gist is outdated! For the most up-to-date information, please see http://emberjs.com/guides/routing/!

It All Starts With Templates

An Ember application starts with its main template. Put your header, footer, and any other decorative content in application.handlebars.

<header>

heckj

cloudenvy:
  keypair_name: heckj
  keypair_location: /home/heckj/.ssh/id_dsa.pub

  clouds:
    env4:
      os_auth_url: http://myopenstack.instance.com:5000/v2.0/
      os_username: heckj
      os_password: **********
      os_tenant_name: heckj-project

preshing

#include <stdio.h>
#include <stdlib.h>
#include <assert.h>

typedef unsigned int u32;
typedef unsigned long long u64;

//-------------------------------------------------------------------------
// WorkArea
//-------------------------------------------------------------------------

jed

(tl;dr DOM builders like [domo][domo] trump HTML templates on the client.)

Like all web developers, I've used a lot of template engines. Like most, I've also written a few of them, some of which even [fit in a tweet][140].

The first open-source code I ever wrote was also one of the the first template engines for node.js, [a port][node-tmpl] of the mother of all JavaScript template engines, [John Resig][jresig]'s [micro-templates][tmpl]. Of course, these days you can't swing a dead cat without hitting a template engine; one in eight packages on npm ([2,220][npm templates] of 16,226 as of 10/19) involve templates.

John's implementation has since evolved and [lives on in Underscore.js][underscore], which means it's the default choice for templating in Backbone.js. And for a while, it's all I would ever use when building a client-side app.

But I can't really see the value in client-side HTML templates anymore.