We use a single monolithic HAProxy to route to all of our applications. We have about 8 different kinds of applications we host. Of those, we have a few separat

We use a single monolithic HAProxy to route to all of our applications. We have about 8 different kinds of applications we host. Of those, we have a few separate instances of those applications available at similar (but different) URLS. Think: `https://sub.domain.com/<prefix>/appname/path` https://sub.domain.com/<prefix>/appname/path`. We route based on `sub`, `prefix`, `appname`, and even sometimes `path`. Managing the config is literally going into this relatively big file, adding in ACLs, adding backends, and setting up the routing rules. We manage the file with puppet, but it's static - not generated. I feel that it's probably time to start deploying many HAProxy instances, generating the file per service, and then maintaining a frontend haproxy that routes according to subdomain. Can anyone comment on similar deployments? Have you found it easier to manage many haproxy instances rather than a single monolithic one?