Google Open Source Load Balancer in Go • Hacker News Board

Re: Google Open Source Load Balancer in Go

#31

Post by softwaredev__ » Sat, Jan 30, 2016, 8:24 PM UTC

I don't want to digress too much from the main discussion, but what are the main reasons people use Go? What are the main use cases for Go? Just looking for a new programming language to learn for some of the next web apps I'll be building.

Re: Google Open Source Load Balancer in Go

#32

Post by forgotpwtomain » Sat, Jan 30, 2016, 8:51 PM UTC

fishnchips wrote: post #25

AYBABTME wrote: post #24

Earlier quoted context omitted.

That analysis is pretty bad, the code is clean and straightforward, yet that tool reports a bunch of random non-issues.

Like near-copy pasta: https://codebeat.co/projects/github-com-google-seesaw/report... ?

It's good etiquette to include a disclaimer, since this code analysis is a tool/company you are affiliated with.

Personally I've never seen any of these code analysis tools produce anything remotely useful. De-duplicating code might be nice in some cases but it certainly has nearly nothing to do with the over-all software quality.

Re: Google Open Source Load Balancer in Go

#33

Post by detaro » Sat, Jan 30, 2016, 8:53 PM UTC

thrownaway2424 wrote: post #20

helper wrote: post #5

Earlier quoted context omitted.

It is a load balancer Google is using in production: http://techcrunch.com/2016/01/29/google-open-sources-its-see... Edit: Here's the official Google announcement: http://google-opensource.blogspot.com/2016/01/seesaw-scalabl...

It's not used in production, it's used in "corp" which is totally disjoint from production at Google.

How is that not "using it in production"? Internal usage is still production usage.

Re: Google Open Source Load Balancer in Go

#34

Post by detaro » Sat, Jan 30, 2016, 8:56 PM UTC

fishnchips wrote: post #25

AYBABTME wrote: post #24

Earlier quoted context omitted.

That analysis is pretty bad, the code is clean and straightforward, yet that tool reports a bunch of random non-issues.

Like near-copy pasta: https://codebeat.co/projects/github-com-google-seesaw/report... ?

Yes, horrible to duplicate standard boilerplate...

Are you adding something to the discussion or are you getting a commission for selling that crappy code quality tool?

EDIT: ok, apparently it is your product. Congratulations on successfully leaving a bad impression.

Re: Google Open Source Load Balancer in Go

#35

Post by bogomipz » Sat, Jan 30, 2016, 9:13 PM UTC

Terretta wrote: post #26

Anycast VIPs and Direct Server Return were a couple key parts of VDN "secret sauce" in early to mid-2000s. Cool to see this engine out in open source. To build a VPN edge you also need cooperative tiered caches with some very counterintuitive cache admission and eviction algorithms, unicast front end with p2p (for vod) or multicast (for live) back end, multi-datacenter event aggregation and correlation, cookieless/db…

I've worked for CDNs and configured many VPNs but I have never heard of a VDN. What is a VDN? I don't recall hearing this term in the early 2000's either. Is that a Google internal name? Could you elaborate? Thanks.

Re: Google Open Source Load Balancer in Go

#36

Post by bogomipz » Sat, Jan 30, 2016, 9:29 PM UTC

Is this just some tooling around Quagga and LVS then? I mean if you had Quagga/BIRD and LVS on your load balancers(not an uncommon configuation) isn't that pretty much all the heavy lifting? What else does Seesaw provide, SSL termination, config management?

Re: Google Open Source Load Balancer in Go

#37

Post by justinsaccount » Sat, Jan 30, 2016, 9:42 PM UTC

bogomipz wrote: post #35

Terretta wrote: post #26

Anycast VIPs and Direct Server Return were a couple key parts of VDN "secret sauce" in early to mid-2000s. Cool to see this engine out in open source. To build a VPN edge you also need cooperative tiered caches with some very counterintuitive cache admission and eviction algorithms, unicast front end with p2p (for vod) or multicast (for live) back end, multi-datacenter event aggregation and correlation, cookieless/db…

I've worked for CDNs and configured many VPNs but I have never heard of a VDN. What is a VDN? I don't recall hearing this term in the early 2000's either. Is that a Google internal name? Could you elaborate? Thanks.

Based on the rest of the commend, VDN = video distribution network. I think the 'VPN' is a typo and should be another 'VDN'

Re: Google Open Source Load Balancer in Go

#38

Post by mwpmaybe » Sat, Jan 30, 2016, 9:48 PM UTC

lobster_johnson wrote: post #12

Official announcement: http://google-opensource.blogspot.com/2016/01/seesaw-scalabl... . Note that this is a network-level load balancer that is tightly coupled with LVS, not a Layer 7 load balancer like HAProxy.

HAproxy can do Layer 4.

Re: Google Open Source Load Balancer in Go

#39

Post by stock_toaster » Sat, Jan 30, 2016, 9:48 PM UTC

matt_wulfeck wrote: post #14

LVS load-balancing is amazing. You can use a tiny instance to load balance huge amounts of traffic since the instance itself doesn't need to process and pass the traffic. the part that makes it difficult to implement is that the hosts have to be on the same network. I didn't dive too much into the code but it looks like you also assign an additional interface to use as a VIP. I believe you'll need to be in your own n…

I wonder why this requires a second interface, as apposed to just an ip alias for the VIP.

Re: Google Open Source Load Balancer in Go

#40

Post by mwpmaybe » Sat, Jan 30, 2016, 9:50 PM UTC

detaro wrote: post #33

thrownaway2424 wrote: post #20

Earlier quoted context omitted.

It's not used in production, it's used in "corp" which is totally disjoint from production at Google.

How is that not "using it in production"? Internal usage is still production usage.

When Google, Facebook, etc. refer to "production" they typically mean google.com, facebook.com, etc.

EDIT: If you're going to down-vote this comment, at least provide detaro with the correct answer to his/her question!