The "sidecar" proxy model reminds me a lot of https://github.com/airbnb/synapse
Linkerd: Twitter-Style Operability for Microservices
11–20 of 39 posts
Re: Linkerd: Twitter-Style Operability for Microservices
#12Suppose I designed something from scratch at former company, and then I decided to reimplement the same project after leaving the company (and perhaps turn that into an open source project), with mostly new code, but similar concept, would that be considered copyright infringement?
are there a lot of companies in the practice of copyrighting their internal architecture and patterns?
Re: Linkerd: Twitter-Style Operability for Microservices
#13This is actually closer to Google-Style operability than it is to Twitter-Style operability. :) Twitter doesn't have an equivalent of GSLB (software load balancer), which is essentially what this is.
Have you seen Google's GSLB? It's not a proxy and it's a rather complex and powerful system. It aggregates and coordinates traffic flow but doesn't directly do any kind of forwarding. You could maybe think of Linkerd like GFE but even still, GFE acts as an edge gateway rather than internal RPC system. This is like a wrapper around stubby or grpc.
Do you have any public resources about Google's GSLB? Searching for it results in general articles about GSLB.
Re: Linkerd: Twitter-Style Operability for Microservices
#14Earlier quoted context omitted.
Have you seen Google's GSLB? It's not a proxy and it's a rather complex and powerful system. It aggregates and coordinates traffic flow but doesn't directly do any kind of forwarding. You could maybe think of Linkerd like GFE but even still, GFE acts as an edge gateway rather than internal RPC system. This is like a wrapper around stubby or grpc.
Do you have any public resources about Google's GSLB? Searching for it results in general articles about GSLB.
I've only ever found two things publicly available on this. The patent related to DNS GSLB http://www.google.com/patents/US7581009 and the video by Simon Newton which describes the global footprint and some of the services https://www.youtube.com/watch?v=DWpBNm6lBU4. Most of what I know about GSLB is from my time working at Google.
Re: Linkerd: Twitter-Style Operability for Microservices
#15The "sidecar" proxy model reminds me a lot of https://github.com/airbnb/synapse
Netflix have something similar https://github.com/Netflix/Prana and I've got a Sidecar in Micro too https://github.com/micro/micro/tree/master/car. It's a solid model for integrating applications which you don't necessarily have client libraries for or don't speak the same protocol.
Re: Linkerd: Twitter-Style Operability for Microservices
#16[Edit: Apparently this is language-agnostic, which wasn't clear from the blog post, so please ignore the complaints below. Will leave them here rather than deleting.]
I loved the pitch, but then I discovered that this is Scala only, which was disappointing.
Sure, if your entire organization runs on the JVM (like Twitter presumably does), then something like this is going to be fine. But many/most organizations use multiple languages, for various reasons. At my company we are currently looking into replacing our current microservie RPC (JSON over HTTP) with something better, and we do need to support Ruby, Go and Node.js, as well as plain HTTP from browsers.
The only viable cross-platform RPC technologies right now are gRPC and Thrift, both of which are rather heavy-handed (lots of IDL + code generation + client/server setup code), and neither of which solve the really hard problems (discoverability, load balancing, fault tolerance, etc.). It's also doubtful that gRPC is really in a usable state yet. Thrift is by far the most mature solution in this space.
Maybe we'll be able to take some inspiration from this project when building our upcoming solution, whatever it will be.
Re: Linkerd: Twitter-Style Operability for Microservices
#17[Edit: Apparently this is language-agnostic, which wasn't clear from the blog post, so please ignore the complaints below. Will leave them here rather than deleting.] I loved the pitch, but then I discovered that this is Scala only, which was disappointing. Sure, if your entire organization runs on the JVM (like Twitter presumably does), then something like this is going to be fine. But many/most organizations use mu…
No no, you're missing the point, it's an RPC proxy which is language agnostic. It sits along side your application as opposed to being a library that you bake in.
Re: Linkerd: Twitter-Style Operability for Microservices
#18[Edit: Apparently this is language-agnostic, which wasn't clear from the blog post, so please ignore the complaints below. Will leave them here rather than deleting.] I loved the pitch, but then I discovered that this is Scala only, which was disappointing. Sure, if your entire organization runs on the JVM (like Twitter presumably does), then something like this is going to be fine. But many/most organizations use mu…
No no, you're missing the point, it's an RPC proxy which is language agnostic. It sits along side your application as opposed to being a library that you bake in.
I see. My fault for going straight to the Github repo rather than to linkerd.io.
Re: Linkerd: Twitter-Style Operability for Microservices
#19Suppose I designed something from scratch at former company, and then I decided to reimplement the same project after leaving the company (and perhaps turn that into an open source project), with mostly new code, but similar concept, would that be considered copyright infringement?
are there a lot of companies in the practice of copyrighting their internal architecture and patterns?
In usa everything that is copyrightable, becomes copyrighted at moment it is created. For instance that sentence, and this on, are protected works owned by me. The only reAson HN can legally use then is cause I gave them license, buried somewhere in Eula/site terms of use.
Also, an architecture is not copyrightable. Maybe patentable. Copyrights protect specific expressions, not a general idea, plan, or architecture. At least not yet thankfully I haven't seen anyone try to argue an unrelated software doing same thing is a derivative work.
Re: Linkerd: Twitter-Style Operability for Microservices
#20Suppose I designed something from scratch at former company, and then I decided to reimplement the same project after leaving the company (and perhaps turn that into an open source project), with mostly new code, but similar concept, would that be considered copyright infringement?
are there a lot of companies in the practice of copyrighting their internal architecture and patterns?
Many big companies will patent their internal architectures. I've been involved in the creation of quite a few patent applications of exactly that. My name is even on one of them.
It's silly and ridiculous but necessary because of the way patents are enforced.
I can promise you that the existence of the patent system did not motivate us to build any of that software, but it certainly motivated us to patent it after the fact, so that someone else couldn't patent it and then sue us for having independently built the same thing.