Author of the blog post here, happy to answer any questions about this release.
Open tracing sounds nice, what info is passed along?
My question is what conversation has there been re: Opentelemetry, the successor to OT
HAProxy 2.4
11–20 of 70 posts
Re: HAProxy 2.4
#12If I have a cloud provider, why might I use HAProxy over the provider's load balancing solution?
Missing capabilities. Some cloud provider load balancers don't support mutual authentication with TLS, for example.
Re: HAProxy 2.4
#13Author of the blog post here, happy to answer any questions about this release.
Open tracing sounds nice, what info is passed along?
You can pass along timing data from every aspect of the request [1] currently there are approximately 20 events supported. You can also send over just about anything that can be stored within an HAProxy variable / header through a tag. Here's an example configuration for HAProxy (simple) [2] (advanced) [3] and the OpenTracing specific configuration (simple) [4] (advanced) [5]. I've included both simple and advanced configurations.
[1] https://github.com/haproxy/haproxy/blob/master/addons/ot/REA...
[2] https://github.com/haproxy/haproxy/blob/master/addons/ot/tes...
[3] https://github.com/haproxy/haproxy/blob/master/addons/ot/tes...
[4] https://github.com/haproxy/haproxy/blob/master/addons/ot/tes...
[5] https://github.com/haproxy/haproxy/blob/master/addons/ot/tes...
Re: HAProxy 2.4
#14Earlier quoted context omitted.
You'd have more specific than "every single cloud provider" but in general HAProxy is way more advanced than most other proxies. Stickiness, rate limiting, gzip compression, configurable logging, caching, Lua scripting, load balancing to domain names, more options for health lifecycle. It even has a control socket to instantly manage the server without restart. HAProxy is actually the inventor the PROXY protocol whic…
Well said, to add to this, HAProxy is also closing the gap on convenience with its recent addition of AWS EC2 service discovery [1] and Consul service discovery integrations [2]. [1] https://www.haproxy.com/blog/announcing-haproxy-data-plane-a... [2] https://www.haproxy.com/blog/announcing-haproxy-data-plane-a...
Wow, cool. HAProxy is coming a long way. Consul integration makes me excited to take another look at using it for our mesh. Using Fabio right now, and it's fine, but I'd love to go back to HAProxy for this if it makes sense.
Re: HAProxy 2.4
#15If I have a cloud provider, why might I use HAProxy over the provider's load balancing solution?
They have very nice features that provider's load balancing might not offer you.
First to me is the ability to retain the IP address. When using AWS Load Balancer, the LB scale automatically and replace the IP.
Second is sophisiciated routing. Example route by cookie. What it buy is that by setting a cookie you can make sure the request hit a specific pool. You can also have concept of backup
Third is lots of useful metrics with their stats page.
Fourth is the ability to alter the responses such as removing header. You have to pair with lambda edge for these on AWS. What it helps is imagine you can write back the user_id to HAProxy, HAProxy log it together with the request, and delete it(so client won't see it). It helps to easily tail the log for a specific user.
And a lot of rate limiting built-in features that just take a few lines of config.
Re: HAProxy 2.4
#16Author of the blog post here, happy to answer any questions about this release.
The added support for FIX is interesting. As far as I can tell it's just TCP-level load balancing, is that right? HAProxy doesn't have the ability to, say, distribute each incoming order to a different backend server?
Re: HAProxy 2.4
#17If I have a cloud provider, why might I use HAProxy over the provider's load balancing solution?
They have very nice features that provider's load balancing might not offer you. First to me is the ability to retain the IP address. When using AWS Load Balancer, the LB scale automatically and replace the IP. Second is sophisiciated routing. Example route by cookie. What it buy is that by setting a cookie you can make sure the request hit a specific pool. You can also have concept of backup Third is lots of useful…
Small note - AWS Network Load Balancers maintain the same IP addresses.
Re: HAProxy 2.4
#18Author of the blog post here, happy to answer any questions about this release.
The added support for FIX is interesting. As far as I can tell it's just TCP-level load balancing, is that right? HAProxy doesn't have the ability to, say, distribute each incoming order to a different backend server?
It has the ability to route by FIX tags. You can find an example here [1]
[1] https://www.haproxy.com/blog/haproxy-enterprise-2-3-and-hapr...
Re: HAProxy 2.4
#19Earlier quoted context omitted.
The added support for FIX is interesting. As far as I can tell it's just TCP-level load balancing, is that right? HAProxy doesn't have the ability to, say, distribute each incoming order to a different backend server?
It has the ability to route by FIX tags. You can find an example here [1] [1] https://www.haproxy.com/blog/haproxy-enterprise-2-3-and-hapr...
Sure, I saw that example. Maybe let me put it a different way: if a client has one inbound FIX connection to HAProxy, can HAProxy connect to N backend servers and send each FIX message from the single client connection to a different backend?
Re: HAProxy 2.4
#20Earlier quoted context omitted.
It has the ability to route by FIX tags. You can find an example here [1] [1] https://www.haproxy.com/blog/haproxy-enterprise-2-3-and-hapr...
Sure, I saw that example. Maybe let me put it a different way: if a client has one inbound FIX connection to HAProxy, can HAProxy connect to N backend servers and send each FIX message from the single client connection to a different backend?
I have not tested that use case but I do not think so. It has the ability to parse FIX tag values and make routing decisions from the initial Logon message.