The New HAProxy Data Plane API: Two Examples of Programmatic Configuration

Re:The New HAProxy Data Plane API: Two Examples of Programma... by cheriot on Monday July 01, 2019 @02:18PM (#20328158)

Are there any fundamental incompatibilities between the HAProxy data plane api and Envoy's?

I wonder if something could sit in between and translate. It would be great for all the existing control planes to work with multiple data plane proxies.

[ Parent | on HN ]

Re:The New HAProxy Data Plane API: Two Examples of Programma... by wtarreau on Monday July 01, 2019 @04:40PM (#20329513)

And to add to this, a few of us at haproxy are part of the UDPA-WG (universal data plane API working group) with Envoy people to help figure how to define a universal/portable data plane API which would work across multiple load balancers. This sounds like a tedious task but your concern definitely proves it's worth the effort.

[ Parent | on HN ]

Re:The New HAProxy Data Plane API: Two Examples of Programma... by bndw on Monday July 01, 2019 @02:30PM (#20328279)

Envoy's xDS APIs work with snapshots of configuration data that are compiled externally and sent to Envoy.

HAProxy's API looks like more of a transactional RPC API and HAProxy manages the configuration internally.

[ Parent | on HN ]

Re:The New HAProxy Data Plane API: Two Examples of Programma... by aiharos on Tuesday July 02, 2019 @06:07AM (#20333666)

Transactions are an optional part of the API to allow change over multiple API resources atomically.

Getting an entire snapshot of configuration data is quite compatible with this, since then the explicit use of transactions is not necessary and the dataplane can take care of it on its own.

[ Parent | on HN ]