Re:Using HAProxy as an API Gateway, Part 1
by rubyn00bie on Tuesday October 02, 2018 @01:09PM
(#18123563)
Anyone have any idea how using HAProxy compares to say Kong?
[ Parent
| on HN ]
Re:Using HAProxy as an API Gateway, Part 1
by graphememes on Tuesday October 02, 2018 @01:23PM
(#18123703)
I had to muck around a lot more to get HAProxy (2-3 days) do what I could do with Kong out of the box (1-2 hours) and Kong was easier to scale for me (simple terraform scripts).
Re:Using HAProxy as an API Gateway, Part 1
by baylisscg on Tuesday October 02, 2018 @08:51PM
(#18126877)
To be honest I'd sat Kong is slightly harder to set up as it wants a database (PostgeSQL or Cassandra) but offers more functionality out of the box. HAProxy is more focused on being … well a proxy for example it can handle straight TCP too.
Its like the PostgreSQL vs ${NoSQL de jour}. HAProxy works fine to great as a default choice unless you've some requirement that makes Kong more attractive.
Re:Using HAProxy as an API Gateway, Part 1
by jaequery on Tuesday October 02, 2018 @06:34PM
(#18126284)
I’ve no experience with Kong but HAproxy is one of the simplest and sturdiest daemon server I have ever used. With just a couple tweaks to the config file, I know exactly what it will do and what it can’t do.