Let's say I have items A, B, and C. I have two backend servers: server01 and server02.
Item A can be handled by server01, item B and C can be handled by server02. New items and servers get added and removed, and we programatically update a hash table between item id and backend server in a file, Redis, Memcache, or similar (whatever the proxy would support).
Can I make a frontend such as /items/${id}
, and have HAProxy route to the correct backend server based on ${id}
? So by looking up what id is associated with what server?
If not, would Nginx be able to do this?
You can use maps to make it work.
This is perfectly outlined in a post on the HAProxy.com blog. They're mapping based on the
Host
header, but it would be trivial to change the config to work for the URL.One extra benefit here is that you can dynamically add and remove mapping entries using the
http-[request|response] [set-map|del-map]
keywords, or via the admin socket.Changes made with
http-[request|response]
or via the socket aren't persisted between reboots, so you'd want to have some out of band process to update the map file at the same time, but that's another question all together.Assuming you have a backend for each server, and given a map file called
/etc/haproxy/items.map
with these contents:You would do something like this in your frontend:
If you have both servers in the same backend, you'd write an ACL in the front-end that catches all the items (
acl items path_beg /items
), send them to the backend (use_backend servers if items
) and replace theuse_backend
line from the frontend with appropriately if-clauseduse_server
lines in the backend.Yes, you can easily do this with HAProxy. Simply create an ACL with a list of IDs served by server and apply it to a use-server directive. IE: