You could say the exact same thing about Varnish. In fact I say your money would...

felipelemos · on April 26, 2017

But varnish lacks some features like dns-backend-resolution that are essential on modern microservices world.

boyter · on April 26, 2017

I keep hearing this as being an issue but when I suggest slinging some money at the guy creating it I never get a response.

Apparently its a big enough issue to grumble about but not big enough to front some cash to resolve.

I agree though. DNS backend lookups for this would be an excellent thing to add.

ruben_varnish · on April 27, 2017

https://docs.varnish-software.com/varnish-cache-plus/vmods/g...

That? Works like a charm.

It's available with the on-premise enterprise subscription and on the AWS and Azure clouds as Varnish Plus - Caching Engine:

https://aws.amazon.com/marketplace/seller-profile?id=263c020...

https://azuremarketplace.microsoft.com/en-us/marketplace/app...

https://www.varnish-software.com/pricing/varnish-plus/

feld · on April 26, 2017

I'm not entirely sure what this is about. Are you saying the list of backends is dynamic and retrieved from DNS? Why would you do this? Why are the backends changing so frequently? This seems like a major design issue. Why not have one backend that's anycasted with equal priority and you can pop backends in and out as you please?

Also, why wouldn't you just solve this with SRV records? Just patch Varnish to support SRV properly and magic you get everything you ever wanted including failover and priorities. That's probably a more sane request.

felipelemos · on April 27, 2017

AWS ELB as backend for example.