24 comments

[ 3.4 ms ] story [ 65.1 ms ] thread
I like this pattern of using a distributed configuration store like etcd for load balancers so you can have a single configuration for a set of frontends. It is also great to have HTTP servers focused on runtime reconfiguration via APIs. A similar project that I have found useful is called Vulcan: http://vulcand.io/
In fact, I'm using https://github.com/mailgun/oxy, the reverse proxy Engine made by Mailgun to build Vulcand :) Vulcand is awsome. But I wanted to build something simpler, that would work not only with etcd, but also with Docker, Mesos, Consul, etc.
I'm very interested in dynamically configured reverse proxies, and this one seems to have a few positive aspects. A few doubts:

* How is the API authenticated?

* Does the API backend persist the configuration?

* Are there any plans for content-modification?

Hi! 1/ TLS 2/ Not for now, but definitely the roadmap 3/ Not in a near futur sorry :)
I would like a comparison of features with haproxy.

TIA!

For a norwegian (ØÆÅ, there you go, proof enough?), seeing someone misspelling traffic as "træfik" immediately makes me think about some guy from out in the country, with a semi-thick norwegian dialect and bad, bad norw-english pronounciation.

"Træfik".

Americanized, with full prejudice, my best træfik character-impression would be "Hey y'all. Howdy doodely do! What'cha got going on here in the barn? Because that ain't no country or western I know!"

You get the picture :)

As a native American English speaker, when I see that, I really want to pronounce it as "tree-fik", in a similar way as we would pronounce caesar... maybe even make it really weird and say "tray-ee-fik" and that just isn't pleasant to say. :)
Etter å ha lært litt norsk det plager meg også.
*Etter å ha lært litt norsk, plager det meg også.
Have you guys done any performance analysis of Træfɪk vs HAProxy vs Nginx?
I have made some tests, but as Træfɪk is still in developpement, I will publish some serious benchmarks later.

Besides, Træfɪk is not in the race of pure performance. It is fast and will be fast, but it's not my top priority.

As long as its performance is not orders of magnitude slower than HAProxy/Nginx, I think it's great that is not your top priority :)
The readme links to a releases page to get some binaries, but afaik it's just source.
Any chance you can add one of those "Fork me on github" banners? Not even having the github url a hyperlink is a bit annoying.
You're absolutely right :) It should be better now.