Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
williamallthing
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
31.
▲
Failure Injection on Kubernetes with SMI and Linkerd
(linkerd.io)
38 points
by
williamallthing
7y ago
|
10 comments
32.
▲
by
williamallthing
7y ago
Linkerd uses <10mb per proxy
33.
▲
by
williamallthing
7y ago
Very cool!
34.
▲
by
williamallthing
7y ago
The service mesh doesn't have to be complex. If you want the value of the service mesh at a fraction of the complexity, start with Linkerd.
35.
▲
by
williamallthing
7y ago
Have you considered doing a similar writeup for Linkerd? ( https://linkerd.io )
36.
▲
by
williamallthing
7y ago
Author here. Happy to answer any questions you might have.
37.
▲
Linkerd 2.3: Towards Zero-Touch, Zero-Trust Networking for Kubernetes
(linkerd.io)
12 points
by
williamallthing
7y ago
|
1 comments
38.
▲
by
williamallthing
8y ago
Is this helpful? https://buoyant.io/2017/04/25/whats-a-service-mesh-and-why-d...
39.
▲
Lessons from Prod Resulted in a Rewrite of Linkerd from Scala to Rust and Go
(infoq.com)
17 points
by
williamallthing
8y ago
|
0 comments
40.
▲
by
williamallthing
8y ago
Thanks, this is a really helpful overview!
41.
▲
by
williamallthing
8y ago
I'm not an expert, but don’t all modern databases suffer from these issues? I thought they all depended on clock sync like Google Spanner.
42.
▲
by
williamallthing
8y ago
FYI Linkerd's Grafana dashboards are purely additive. If you don't like them, ignore them. We also work hard to make Linkerd incremental. It doesn't "touch every TCP connection" so much as "touch every TCP conn
43.
▲
by
williamallthing
8y ago
Distributed tracing requires instrumentation / app modification (for header forwarding if nothing else), but metrics don't. E.g. Linkerd gives you service "golden metrics" (success rate, latency distribution, request vol
44.
▲
by
williamallthing
8y ago
What consistency model does FDB provide?
45.
▲
GRPC Load Balancing on Kubernetes Without Tears
(kubernetes.io)
17 points
by
williamallthing
8y ago
|
0 comments
46.
▲
by
williamallthing
8y ago
You can start with Linkerd 1.x today. Supports pretty much every platform. :)
47.
▲
by
williamallthing
8y ago
Exactly! We considered Go briefly but in the end, the magic intersection of native-code performance, plus guaranteed memory safety, trumped every other concern for the data plane.
48.
▲
by
williamallthing
8y ago
The article this quote is pulled from [1] is primarily referring to Linkerd 1.x, but Istio follows the same patterns. [1] https://blog.linkerd.io/2018/09/18/announcing-linkerd-2-0/
49.
▲
by
williamallthing
8y ago
Those quotes aren't from the article. I'll address them anyways since they're from a different article which I wrote: >> "Traditional service meshes are an all-or-nothing proposition that add a significant layer of
50.
▲
by
williamallthing
8y ago
There's a PR open! https://github.com/linkerd/linkerd2/pull/1423
51.
▲
by
williamallthing
8y ago
Just a question of starting point. Linkerd 1.x has been running for years on multiple platforms, and we'll get there with the 2.x line as well.
52.
▲
by
williamallthing
8y ago
Linkerd person here. The two projects have very different goals. I wrote some more about this on the Linkerd blog: https://blog.linkerd.io/2018/09/18/announcing-linkerd-2-0/
53.
▲
by
williamallthing
8y ago
I'm biased, but Linkerd has been in prod at companies around the world for almost 2 years so it's about as mature as it gets. If you're moving to Kubernetes, you're also a candidate for Conduit (next generation ultraligh
54.
▲
by
williamallthing
8y ago
The dashboards are a detail, but visibility into topline service metrics are absolutely critical. There's a huge difference between "I need to configure a bunch of stuff and do some complicated things first", and "I get
55.
▲
by
williamallthing
8y ago
Yep, shouldn't be too hard
56.
▲
by
williamallthing
8y ago
Did I mention focused on solving real problems with a minimum of fuss? If you can't get topline metrics dashboards for every service you're running in Kubernetes within 60 seconds of installing Conduit, I will literally* send a te
57.
▲
by
williamallthing
8y ago
Conduit's a tool to solve actual, engineering-facing operational problems with as little complexity as possible, that happens to be a service mesh. Istio is a Big Important Service Mesh for Big Important People that does everything und
58.
▲
by
williamallthing
8y ago
Thanks! We've got a couple more features coming up along this vein that you're really going to like.
59.
▲
by
williamallthing
8y ago
Thanks! Yeah, that's the danger of putting up a public roadmap with dates on it. We've seen a little production usage that uncovered a couple issues that we wanted to address quickly, and that shifted the timeline a bit. But we&#x
60.
▲
Debugging microservices on Kubernetes with the Conduit service mesh 0.4 release
(buoyant.io)
52 points
by
williamallthing
8y ago
|
13 comments
More ›