Re: [VOTE] linkerd project proposal

Camille Fournier


On Jan 14, 2017 4:26 PM, "Benjamin Hindman via cncf-toc" <cncf-toc@...> wrote:

On Fri, Jan 13, 2017 at 7:49 AM, Chris Aniszczyk via cncf-toc <cncf-toc@...> wrote:
Hey CNCF TOC community, it's time to vote on the linkerd ( proposal as an inception level project, you can view the proposal below in this email or on GitHub:

Please vote +1/0/-1


Name of project: linkerd

Description: Linkerd is an open source service mesh for cloud-native applications. It is a layer 5/7 proxy that provides fully decentralized request-level reliability and optimization to service communication, including latency-aware load balancing, retries, failure handling, circuit breaking, and deadlines. It provides granular metrics (both of itself and of downstream services), distributed tracing, TLS, a powerful logical routing layer, and integration with most common service discovery mechanisms.

Applications use linkerd by proxying HTTP, gRPC, or Thrift calls through a local linkerd instance. In many cases, integration with linkerd is a config change (e.g. setting an http_proxy environment variable) rather than a code change. Linkerd acts as a transparent proxy, and so a call to (e.g. "http://foo/bar") will be routed to the appropriate cluster, resolved in service discovery, load balanced, retried, and returned without application code being aware.

Linkerd is built on top of Finagle (, the high-concurrency RPC library that powers companies like Twitter, Soundcloud, Pinterest, and ING Bank. By staying close to the Finagle codebase, linkerd takes advantage of Finagle’s extensive production usage ( Linkerd’s primary author is a core contributor to Finagle.

Sponsor / Advisor from TOC:
Jonathan Boulle <jonathan.boulle@...>

Unique Identifier: linkerd

License: Apache License v2.0

Maturity Level: Inception

Source control repositories:

Initial Committers (leads): Oliver Gould (Buoyant) [@olix0r] and Alex Leong (Buoyant) [@adleong]

Infrastructure requirements: CI and potentially CNCF Community Cluster access. We run integration tests per commit (e.g. testing Kubernetes API integration) and periodic high-volume stress tests.

Issue tracker:

Mailing lists:!forum/linkerd-users


Community: Active & growing!

Primarily focused on (~400 members)

~1200 GitHub stars

~25 contributors

Release methodology and mechanics: Code review on all changes. Releases triggered manually by developer team. Using pre-1.0 semver semantics.

Social media accounts: Twitter: @linkerd, Slack:

Existing sponsorship:

External Dependencies: Runtime: JVM. Build-time: Finagle, netty

Statement on alignment with CNCF mission:

Linkerd directly addresses the communications challenges of running microservices at scale, and integrates directly with orchestrated environments such as Kubernetes and DC/OS. Linkerd integrates with two existing CNCF projects: it can use the Kubernetes API directly as a service discovery mechanism, and it exposes metrics in Prometheus format. See this blog post ( for an example of linkerd, Kubernetes and Prometheus working together.

Production Usage:

Monzo: used in production; k8s-based infra (

NCBI: used in production w/Consul

Quid: used in production

Douban: used in production

Houghton Mifflin Harcourt: used in production; DC/OS-based infra

Olark: used in production; k8s-based infra (

Other Contributors:

Currently ~25; >50% non-Buoyant by headcount:

Chris Aniszczyk (@cra) | +1-512-961-6719

cncf-toc mailing list

Benjamin Hindman
Founder of Mesosphere and Co-Creator of Apache Mesos

Follow us on Twitter: @mesosphere

Watch the Video .Learn how Verizon serves millions
of users in real time with DC/OS

cncf-toc mailing list

Join { to automatically receive all group messages.