Proxy

[sirupsen]

If Semian was a proxy it'd be simpler to use, and could be opt-out instead of opt-in for apps in an organization.

Some inspriation could be taken from: https://github.com/vektra/templar

It possibly would be re-implemented in something like Go. This also solves issues such as sharing state between containers.

[rud]

I believe I've heard HAProxy configured for this particular use-case of TCP connection proxying to external services. Might be an awesome way to save a lot of effort just to wrap / elegantly configure that. Only a thought.

[sirupsen]

HAProxy has poor support for on-the-fly reloading (by dropping connections). HAProxy is more suited for situations that require load balancing and/or health checking (eg Airbnb's smart stack), which Semian doesn't. It can't be scripted to do anything advanced like Semian does. the cool thing about the proxy is that we don't need to look at L4/L3 at all, but can merely observerve remote ACK times.

[rud]

Did not realize, thank you for the feedback. Carry on :)

[sirupsen]

ya of course :) I'll be sure to do a talk on this next time I'm in Aarhus.