williamallthing

10 ms·

61.
by williamallthing 9y ago
Spot on. FWIW with some effort we can get Linkerd down to ~110mb. For some companies that's acceptable. Still, it's a far cry from the ~3mb footprint that the Conduit proxies current have.
62.
by williamallthing 9y ago
You might like this post: https://blog.buoyant.io/2017/01/31/making-things-faster-by-a...
63.
Linkerd-tcp: A lightweight, service-discovery-aware, TLS-ing TCP load balancer(blog.buoyant.io)
170 points by williamallthing 10y ago|15 comments
64.
A Service Mesh for Kubernetes: Distributed Tracing(blog.buoyant.io)
14 points by williamallthing 10y ago|0 comments
65.
by williamallthing 10y ago
Howdy, Linkerd person here. Always nice to have a surprise Hacker News frontpage post! Please let me know if you have any questions. We also have a very active Slack at slack.linkerd.io. Hop on in and say hello.
66.
by williamallthing 10y ago
Partially inspired by the soundcloud post here: https://developers.soundcloud.com/blog/lessons-in-resilience...
67.
HTTP/2, gRPC, and the future of linkerd(blog.buoyant.io)
10 points by williamallthing 10y ago|0 comments
68.
A Service Mesh for Kubernetes, Part III: Encrypting All the Things(blog.buoyant.io)
16 points by williamallthing 10y ago|0 comments
69.
by williamallthing 10y ago
You'll be happy to know that linkerd works really well on DC/OS as well. :) https://blog.buoyant.io/2016/10/10/linkerd-on-dcos-for-servi...
70.
by williamallthing 10y ago
Great point about the need for production worthiness. FWIW the load balancing pool management, etc., in linkerd is straight from Finagle, which is probably more proven than Kubernetes, if anything (powers Twitter, Pinterest, SoundCloud, e
71.
by williamallthing 10y ago
Request-level versus connection-level load balancing. See e.g. https://blog.buoyant.io/2016/03/16/beyond-round-robin-load-b...
72.
Squeezing blood from a stone: small-mem JVM techniques for microservice sidecars(blog.buoyant.io)
6 points by williamallthing 10y ago|0 comments
73.
by williamallthing 11y ago
You may be interested in linkerd ( https://linkerd.io ) -- we built it specifically to address the complexity of proper connection management at scale (service discovery, timeouts, loadbalancing, retry policies). Extends to routin
74.
by williamallthing 11y ago
I'm curious to hear what your experience with NATS will be. We haven't played with it. I do know that a ton of the work that went into Finagle was around resilience at scale: things like backpressure, circuit breaking, and general
75.
by williamallthing 11y ago
Yup, absolutely. Any requests? :)
76.
by williamallthing 11y ago
We can definitely improve the docs a bit on this point. But FWIW we totally agree with you. Finagle itself is a JVM library, and that worked well enough at Twitter [insert caveats here], but a big part of the reason we built linkerd is exte
77.
by williamallthing 11y ago
Hey, thanks for the thoughtful comment! Here are some quick answers to your questions: - Routing to 3rd party services: on the roadmap! - Circuit breaking: Finagle has some very sophisticated mechanisms for this (see http://twitt
78.
Linkerd: Twitter-Style Operability for Microservices(blog.buoyant.io)
13 points by williamallthing 11y ago|2 comments
79.
How to rank products based on user input(all-thing.net)
1 points by williamallthing 16y ago|0 comments
80.
by williamallthing 17y ago
I'm working on Sup, the email client for nerds. http://sup.rubyforge.org .
81.
by williamallthing 17y ago
not really. there's a lot of chinese characters pronounced "bing", especially since the tone is unspecified. look at e.g. http://zhongwen.com/s/v19.htm -- the first three rows are all "bing" characters.
82.
Some git fu(all-thing.net)
2 points by williamallthing 18y ago|0 comments