Conduit Alternatives

Reviews and mentions

• Nginx – The Architecture of Open Source Applications
  5 projects | news.ycombinator.com | 2 Nov 2021

  > As a relatively young dev, the idea of a "web server" as a standalone binary that serves your application (vs a library that you use to write your own "server") feels strange.

  In my eyes, the ideal setup is one that's layered: where you have an ingress that's basically a load balancer that also ensures that you have SSL/TLS certificates, enforces rate limits, perhaps is used for some very basic logging, or can optionally do any URL rewriting that you need. Personally, i think that Caddy (https://caddyserver.com/) is lovely for this, whereas some people prefer something like Traefik (https://traefik.io/), though the older software packages like Nginx (https://nginx.org/en/) or even Apache (https://www.apache.org/) are good too, as long as the pattern itself is in place.

  Then, you may additionally have any sorts of middleware that you need, such as a service mesh for service discovery, or providing internal SSL/TLS - personally Docker Swarm (https://docs.docker.com/engine/swarm/) overlay networks have always been enough for me in this regard, though some people enjoy other solutions, such as Hashicorp Consul (https://www.consul.io/), or maybe something intended for Kubernetes or other platforms that you already may be using, like Linkerd (https://linkerd.io/).

  Finally, you have your actual application with its server. Personally, i think that the web server should be embedded (for example, embedded Tomcat with Spring Boot) or indeed just be a library that's a part of the application executable, as long as you can update it easily enough by rebuilding the application - containers are good for this, but aren't strictly necessary, since sometimes other forms of automation and packaging are also enough.

  The reason why i believe this, is because i've seen plenty of deployments where that just isn't the case:

    - attempts to store certificates within the application, each application server having different requirements for the formats to be used, making management (and automation) of renewal a total nightmare

• Implementing Istio in a Kubernetes cluster
  7 projects | dev.to | 25 Oct 2021

  Linkerd

• From Monolith to Microservices and Beyond
  5 projects | dev.to | 5 Oct 2021

  A Service Mesh is a dedicated and configurable infrastructure layer with the intent of handling network-based communication between services. Istio and Linkerd are two examples of implementations. Most implementations usually have two main components: the Control plane and the Data plane. The Control plane manages and configures the proxies that compose the Data plane. Those Data plane proxies are deployed as sidecars and can provide functionalities like service discovery, retries, timeouts, circuit breaking, fault injection, and much more.

• Linkerd 2.11 now includes a Kubernetes controller written in Rust
  5 projects | reddit.com/r/rust | 1 Oct 2021

  Linkerd--a service mesh for Kubernetes--has featured a proxy written in Rust (since ~2017), but its control plane has been implemented entirely in Go... until now!

  5 projects | reddit.com/r/rust | 1 Oct 2021

  With yesterday's 2.11.0 release, Linkerd features a new policy-controller component written in Rust! It uses kube-rs to communicate with the Kubernetes API and it exposes a gRPC API implemented with Tonic.

• Announcing Linkerd 2.11: Policy, gRPC retries, performance improvements, and more!
  1 project | reddit.com/r/linkerd | 30 Sep 2021

  See https://github.com/linkerd/linkerd2/pull/5967 for more info

• How Linkerd uses iptables to transparently route Kubernetes traffic
  1 project | reddit.com/r/linkerd | 25 Sep 2021

  I, personally, have been waiting for more news on bpfilter. If you have some thoughts around supporting it though (perhaps alongside iptables), then we'd welcome an issue on GitHub :)

• Request routing for horizontally scaled services
  6 projects | dev.to | 8 Aug 2021

  The myriad of request processing middlewares does not end here - there is also the very trendy topic of service meshes that we could cover, but I choose to leave that as an exercise to interested readers, as it is a rapidly evolving and complex space (see: Istio, linkerd, Consul, Tanzu, etc).

• Upcoming trends in DevOps and SRE
  8 projects | dev.to | 20 Jul 2021

  Some examples of open source service meshes are Istio, Linkerd and Kuma. Service meshes provide a comprehensive view of your service and aid with complex activities like A/B testing, canary roll-outs, access restrictions, and end-to-end authentication.

• Introducing the Cloud Native Compute Foundation (CNCF)
  6 projects | dev.to | 13 Jul 2021

  In the episode with Annie, she gave a great overview of the CNCF and a handful of projects that she's excited about. Those include Helm, Linkerd, Kudo, Keda and Artifact Hub. I gave a bonus example of the Service Mesh Interface project.

• Issue installing stable-2.10.2 on AKS
  1 project | reddit.com/r/linkerd | 18 Jun 2021

  It's hard to now what the issue is from these screenshots alone. If you see this again, it would be great if you could run kubectl describe and kubectl logs ... on these pods and then share that information in an issue.

• Benchmarks: Linkerd vs Istio
  2 projects | reddit.com/r/kubernetes | 27 May 2021

  Totally agree. This is why we had the folks at Kinvolk (now part of microsoft) build out the benchmarking harness as an open source tool. And why we've published the setup we've used.

• Linkerd.io – Self-hosted Kubernetes without the complexity
  1 project | news.ycombinator.com | 19 Mar 2021