We are currently using synapse instances (https://github.com/airbnb/synapse?) as client-side loadbalancers next to our our individual python services. Linkerd sounds like a capable drop-in replacement. Great!
________________________________ From: [email protected] <[email protected]> Sent: Thursday, May 5, 2016 23:28 To: [email protected] Subject: Re: interested in a fast service load balancer / proxy? I've got a set of aurora configs for linkerd that I can share after cleaning them up a bit; stay tuned, unless someone else beats me to it. On Thu, May 5, 2016 at 5:17 PM William Morgan <[email protected]<mailto:[email protected]>> wrote: Great idea, let me ask some of our Aurora users and see if we can get an example config from them. -William On Thu, May 5, 2016 at 7:42 AM, Rogier Dikkes <[email protected]<mailto:[email protected]>> wrote: Are there any plans to provide examples for Aurora+linkerd (as done for kubernetes & mesos+marathon) to give new users an easy way to take linkerd into consideration? On 5/5/16 3:21 AM, William Morgan wrote: Oh, great point. Should have mentioned that. linkerd does indeed speak ServerSets out of the box. On Wednesday, May 4, 2016, Zameer Manji <<mailto:[email protected]>[email protected]<mailto:[email protected]>> wrote: Since linkerd is built upon Finagle, it should automatically work with the ServerSets created by the Announcer in the executor. It should be fairly easy to try out linkerd if you already use Aurora. On Wed, May 4, 2016 at 3:53 PM, William Morgan <[email protected]<mailto:[email protected]>> wrote: [cross posting from the Mesos users' list by popular demand] Dear Aurora friends, We have an open source load balancer / proxy called linkerd<https://linkerd.io/> that might be of interest to some of you. Similar to things like SmartStack's Synapse and marathon-lb, it's a request-level load balancer that speaks to service discovery. However, it doesn't require process restarts when SD updates. It's built on Finagle, Twitter's high-volume RPC library, which means it also can do intelligent things with slow and failing servers, connection pooling, etc. It features pluggable service discovery backends (Zookeeper, Marathon, Consul, etcd), and pluggable protocol support (HTTP, thrift and mux). It's designed as a sort of out-of-process client-side network stack for high-volume service communication, but you can also use it as a debug proxy or an edge traffic server. If that sounds interesting, check out linkerd.io<https://linkerd.io/> for more details, or join us on our Slack channel<http://slack.linkerd.io/>. We'll be presenting it at ApacheCon<http://sched.co/6OJA> and at MesosCon<http://sched.co/6jta> later this month. In the mean time, here's a screenshot to whet your appetite: [cid:[email protected]] ?? Feel free to hit me up with any questions! -William -- Zameer Manji -- -William -- Rogier Dikkes Systeem Programmeur Hadoop & HPC Cloud e-mail: [email protected]<mailto:[email protected]> | M: +31 6 47 48 93 28 SURFsara | Science Park 140 | 1098 XG Amsterdam
