Wow, on a side note, when I saw it I almost thought it was the scammy Israel company that used to thrust adware/malware through its toolbars back then. [1] http://malware.wikia.com/wiki/Conduit_Search
Haha, I remember them. (sighs)
Conduit 0.5.0 and the future of Conduit
11–12 of 12 posts
Re: Conduit 0.5.0 and the future of Conduit
#12One of the biggest draws of Linkerd over Envoy (prior to Consul Connect at least) was that it seemed more feasible to use outside of Kubernetes. Conduit however is tightly coupled to Kubernetes as I understand, which isn’t really addressed in this blog post.
I think many people believe that Kubernetes has won and this where the money is. Big Co’s will be looking for contract support for anything they run on kubernetes.
I mean, clearly Kubernetes has won. That shouldn't be a matter of debate when Mesosphere is doing product releases with top-line functionality designed to make it easier for you to operate Kubernetes.[1]
And Swarm has been a clear loser for a while now.
I say this despite us running a reasonably sized Aurora/Mesos deployment! Three years ago this was probably the right choice. Today I think you end up debating things like whether or not you should go with self-hosting Kubernetes vs managed vs what Mesosphere is pitching now.